這是歷史版本頁面 — 看 PostgreSQL (64-bit) 最新版本
PostgreSQL 是什麼,跟 MySQL 有什麼差別
你正在開發一個新專案,資料量才幾萬筆,但查詢速度已經開始變慢;或者你想把分散在 Excel 和 CSV 裡的資料整理成能多人同時讀寫的格式。你打開搜尋引擎,看到一堆資料庫軟體的名字,卻不確定哪一個才適合自己——你需要的是一個能長期存放資料、支援複雜查詢、而且不會因為流量變大就垮掉的方案。
很多人第一個想到的是把資料繼續放在 Excel 或輕量型資料庫裡,但當資料量成長、需要多人同時寫入、或要做跨表格關聯查詢時,這些方案會開始卡住。這類工具的切入點是:用結構化的表格儲存資料,透過標準的 SQL 語法來查詢與管理,並提供交易保護機制,確保資料在寫入過程中不會因為意外中斷而損壞。PostgreSQL 就是這個領域裡歷史悠久、且持續在更新的開源選擇之一。
01PostgreSQL 跟 MySQL 差在哪裡?
兩者都是開源的關聯式資料庫,但 PostgreSQL 在功能上支援更多進階特性,例如自訂資料型別、部分索引、JSON/JSONB 文件儲存,以及更完整的交易隔離層級。MySQL 則以簡單易用和廣泛部署聞名。如果你的專案需要複雜查詢、地理空間資料或嚴格的資料完整性,PostgreSQL 的內建功能會更直接;若只是簡單的讀寫且團隊已熟悉 MySQL,沿用 MySQL 也能勝任。
02這套軟體能處理多大的資料量?
官方文件指出單一資料表可達 32 TB,並支援表格分割(partitioning)來分散大型資料集的儲存與查詢負擔。實際能跑多順,取決於硬體記憶體、磁碟型態和查詢語法的撰寫方式。建議先以你的真實資料量做壓力測試,確認索引和查詢計畫的執行效率,再決定是否要導入。
03它支援哪些資料型別?
涵蓋常見的整數、數值、字串、布林值、日期時間,也包含陣列、範圍、UUID、JSON/JSONB、XML、key-value(Hstore)以及幾何資料型別如點、線、圓、多邊形。此外可以自訂複合型別。這代表你不需要為了存 JSON 或座標資料另外找工具,同一套資料庫就能處理。
04要怎麼保證資料不會因為突然斷電或當機而損壞?
它實作 Write-ahead Logging(WAL),在資料真正寫入資料表前,會先把變更記錄到日誌中。若系統崩潰,重啟時會依據 WAL 進行復原,確保交易要嘛完整執行、要嘛完全沒發生。也支援同步與非同步複製,可以建立備援節點,並提供 point-in-time-recovery(PITR)把資料回復到過去某個時間點。
05多人同時讀寫同一筆資料會不會鎖住整張表?
它採用 Multi-Version Concurrency Control(MVCC),讓讀取和寫入不會互相阻擋。每個交易看到的是自己開始時的資料快照,寫入時只鎖定必要的列,而不是整張表。因此同時間大量使用者查詢、偶爾有更新時,系統仍能維持順暢。若需要更嚴格的控管,也提供明確鎖定(explicit locks)與建議鎖定(advisory locks)。
06這套軟體適合什麼樣的人用?
適合需要處理結構化資料、且查詢邏輯較複雜的開發者或資料分析師。例如要做多表關聯、子查詢、視窗函數,或需要存放 JSON 文件與地理資訊的應用。它也適合重視資料完整性與交易安全性的場景,像是金流紀錄、訂單系統。若你只是要存簡單的鍵值對,用 SQLite 或 key-value store 會更輕量。
07我完全不會寫 SQL,能用這套軟體嗎?
可以,但門檻較高。它內建的 pgAdmin 提供圖形介面,能建立資料庫、執行查詢、備份還原,不過日常操作仍需要理解基本的 SQL 語法,例如 SELECT、INSERT、UPDATE、DELETE。官方文件完整,但介面是英文。若完全不想碰 SQL,可以考慮用現成的資料庫管理工具(如 DBeaver)搭配視覺化查詢功能,但底層邏輯還是繞不開 SQL。
08什麼情況不該選 PostgreSQL?
如果你的需求只是單機應用程式暫存資料、且不想管理伺服器,SQLite 會更簡單——它不需要安裝、設定或維護,直接以檔案形式運作。若你只需要一個快速的全文字搜尋引擎,Everything Search Engine 那類工具更合適。另外,若團隊完全沒有資料庫管理經驗,且預算無法負擔專人維護,PostgreSQL 的效能調校和升級都需要手動處理,可能超出你的負荷。
09它需要多少硬體資源?
官方建議最低 2GB RAM、4GB 以上較佳,安裝本身需 100MB 以上空間,實際資料量另計。處理器需為 Intel 或 AMD 64 位元。記憶體越大,快取和排序效能越好;若同時連線數高,CPU 和記憶體需求會明顯上升。它沒有內建圖形管理介面,需額外安裝 pgAdmin 或使用命令列工具,這點在評估資源時也要算進去。
10它的授權方式會不會有商業使用的限制?
它是 Open Source 授權,可以免費使用、修改和散布,包含商業用途。沒有授權費或使用者數限制。不過要注意,它採用 PostgreSQL License,這是一種寬鬆的開源授權,允許你將它整合進商業產品中,但若你修改了原始碼並散布,需保留版權聲明。詳細條款建議閱讀官方授權文件確認。
11這套軟體多久更新一次?
根據收錄紀錄,近 12 個月更新 10 次,近 24 個月 20 次,屬於持續活躍開發的專案。官方會定期釋出主要版本和安全性修補,但升級主要版本時可能需要手動調整設定或檢查相容性。建議追蹤官方發布公告,並在測試環境先驗證再升級正式環境。
12它跟 MySQL Workbench 有什麼不同?
MySQL Workbench 是 MySQL 的圖形化管理工具,本身不是資料庫伺服器。PostgreSQL 是資料庫伺服器,官方提供的 pgAdmin 才是它的管理介面。若你習慣用 MySQL Workbench 的視覺化設計和備份功能,PostgreSQL 的 pgAdmin 也有類似功能,但介面和操作邏輯不同。兩者無法直接互換,需重新熟悉工具。
下載與官方連結
postgresql-9.5.3-1-windows-x64.exe · 60.96 MB · 連結指向軟體原廠
版本紀錄
- 2026-10-17 PostgreSQL 18.6 358 MB
- 2026-05-18 PostgreSQL 16.14 349 MB
- 2026-05-17 PostgreSQL 17.10 357 MB
再看 5 筆
- 2026-05-15 PostgreSQL 18.4 357 MB
- 2026-02-27 PostgreSQL 16.13 347 MB
- 2026-02-27 PostgreSQL 17.9 354 MB
- 2026-02-27 PostgreSQL 18.3 355 MB
- 2026-02-13 PostgreSQL 17.8 354 MB
這一版改了什麼
What's new in this version:
- Clear the OpenSSL error queue before OpenSSL calls, rather than assuming it's clear already; and make sure we leave it clear afterwards (Peter Geoghegan, Dave Vitek, Peter Eisentraut)
- This change prevents problems when there are multiple connections using OpenSSL within a single process and not all the code involved follows the same rules for when to clear the error queue. Failures have been reported specifically when a client application uses SSL connections in libpq concurrently with SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL. It's possible for similar problems to arise within the server as well, if an extension module establishes an outgoing SSL connection.
- Fix "failed to build any N-way joins" planner error with a full join enclosed in the right-hand side of a left join (Tom Lane)
- Fix incorrect handling of equivalence-class tests in multilevel nestloop plans (Tom Lane)
- Given a three-or-more-way equivalence class of variables, such as X.X = Y.Y = Z.Z, it was possible for the planner to omit some of the tests needed to enforce that all the variables are actually equal, leading to join rows being output that didn't satisfy the WHERE clauses. For various reasons, erroneous plans were seldom selected in practice, so that this bug has gone undetected for a long time.
- Fix corner-case parser failures occurring when operator_precedence_warning is turned on (Tom Lane)
- An example is that SELECT (ARRAY[])::text[] gave an error, though it worked without the parentheses.
- Fix query-lifespan memory leak in GIN index scans (Julien Rouhaud)
- Fix query-lifespan memory leak and potential index corruption hazard in GIN index insertion (Tom Lane)
- The memory leak would typically not amount to much in simple queries, but it could be very substantial during a large GIN index build with high maintenance_work_mem.
- Fix possible misbehavior of TH, th, and Y,YYY format codes in to_timestamp() (Tom Lane)
- These could advance off the end of the input string, causing subsequent format codes to read garbage.
- Fix dumping of rules and views in which the array argument of a value operator ANY (array) construct is a sub-SELECT (Tom Lane)
- Disallow newlines in ALTER SYSTEM parameter values (Tom Lane)
- The configuration-file parser doesn't support embedded newlines in string literals, so we mustn't allow them in values to be inserted by ALTER SYSTEM.
- Fix ALTER TABLE ... REPLICA IDENTITY USING INDEX to work properly if an index on OID is selected (David Rowley)
- Avoid possible misbehavior after failing to remove a tablespace symlink (Tom Lane)
- Fix crash in logical decoding on alignment-picky platforms (Tom Lane, Andres Freund)
- The failure occurred only with a transaction large enough to spill to disk and a primary-key change within that transaction.
- Avoid repeated requests for feedback from receiver while shutting down walsender (Nick Cleaton)
- Make pg_regress use a startup timeout from the PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
- This is for consistency with a behavior recently added to pg_ctl; it eases automated testing on slow machines.
- Fix pg_upgrade to correctly restore extension membership for operator families containing only one operator class (Tom Lane)
- In such a case, the operator family was restored into the new database, but it was no longer marked as part of the extension. This had no immediate ill effects, but would cause later pg_dump runs to emit output that would cause (harmless) errors on restore.
- Fix pg_upgrade to not fail when new-cluster TOAST rules differ from old (Tom Lane)
- pg_upgrade had special-case code to handle the situation where the new PostgreSQL version thinks that a table should have a TOAST table while the old version did not. That code was broken, so remove it, and instead do nothing in such cases; there seems no reason to believe that we can't get along fine without a TOAST table if that was okay according to the old version's rules.
- Fix atomic operations for PPC when using IBM's XLC compiler (Noah Misch)
- Reduce the number of SysV semaphores used by a build configured with --disable-spinlocks (Tom Lane)
- Rename internal function strtoi() to strtoint() to avoid conflict with a NetBSD library function (Thomas Munro)
- Fix reporting of errors from bind() and listen() system calls on Windows (Tom Lane)
- Reduce verbosity of compiler output when building with Microsoft Visual Studio (Christian Ullrich)
- Support building with Visual Studio 2015 (Michael Paquier, Petr Jelínek)
- Fix putenv() to work properly with Visual Studio 2013 (Michael Paquier)
- Avoid possibly-unsafe use of Windows' FormatMessage() function (Christian Ullrich)
- Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where appropriate. No live bug is known to exist here, but it seems like a good idea to be careful.
- Update time zone data files to tzdata release 2016d for DST law changes in Russia and Venezuela. There are new zone names Europe/Kirov and Asia/Tomsk to reflect the fact that these regions now have different time zone histories from adjacent regions.