這是歷史版本頁面 — 看 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-10.1-2-windows-x64.exe · 連結指向軟體原廠
版本紀錄
- 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:
- Ensure that INSERT ..ON CONFLICT DO UPDATE checks table permissions and RLS policies in all cases (Dean Rasheed)
- The update path of INSERT ..ON CONFLICT DO UPDATE requires SELECT permission on the columns of the arbiter index, but it failed to check for that in the case of an arbiter specified by constraint nameIn addition, for a table with row level security enabled, it failed to check updated rows against the table's SELECT policies (regardless of how the arbiter index was specified)(CVE-2017-15099)
- Fix crash due to rowtype mismatch in json{b}_populate_recordset() (Michael Paquier, Tom Lane)
- These functions used the result rowtype specified in the FROM ..AS clause without checking that it matched the actual rowtype of the supplied tuple valueIf it didn't, that would usually result in a crash, though disclosure of server memory contents seems possible as well(CVE-2017-15098)
- Fix sample server-start scripts to become $PGUSER before opening $PGLOG (Noah Misch)
- Previously, the postmaster log file was opened while still running as rootThe database owner could therefore mount an attack against another system user by making $PGLOG be a symbolic link to some other file, which would then become corrupted by appending log messages.
- By default, these scripts are not installed anywhereUsers who have made use of them will need to manually recopy them, or apply the same changes to their modified versionsIf the existing $PGLOG file is root-owned, it will need to be removed or renamed out of the way before restarting the server with the corrected script(CVE-2017-12172)
- Fix BRIN index summarization to handle concurrent table extension correctly (Álvaro Herrera)
- Previously, a race condition allowed some table rows to be omitted from the indexIt may be necessary to reindex existing BRIN indexes to recover from past occurrences of this problem.
- Fix possible failures during concurrent updates of a BRIN index (Tom Lane)
- These race conditions could result in errors like “invalid index offnum” or “inconsistent range map”.
- Prevent logical replication from setting non-replicated columns to nulls when replicating an UPDATE (Petr Jelinek)
- Fix logical replication to fire BEFORE ROW DELETE triggers when expected (Masahiko Sawada)
- Previously, that failed to happen unless the table also had a BEFORE ROW UPDATE trigger.
- Fix crash when logical decoding is invoked from a SPI-using function, in particular any function written in a PL language (Tom Lane)
- Ignore CTEs when looking up the target table for INSERT/UPDATE/DELETE, and prevent matching schema-qualified target table names to trigger transition table names (Thomas Munro)
- This restores the pre-v10 behavior for CTEs attached to DML commands.
- Avoid evaluating an aggregate function's argument expression(s) at rows where its FILTER test fails (Tom Lane)
- This restores the pre-v10 (and SQL-standard) behavior.
- Fix incorrect query results when multiple GROUPING SETS columns contain the same simple variable (Tom Lane)
- Fix query-lifespan memory leakage while evaluating a set-returning function in a SELECT's target list (Tom Lane)
- Allow parallel execution of prepared statements with generic plans (Amit Kapila, Kuntal Ghosh)
- Fix incorrect parallelization decisions for nested queries (Amit Kapila, Kuntal Ghosh)
- Fix parallel query handling to not fail when a recently-used role is dropped (Amit Kapila)
- Fix crash in parallel execution of a bitmap scan having a BitmapAnd plan node below a BitmapOr node (Dilip Kumar)
- Fix json_build_array(), json_build_object(), and their jsonb equivalents to handle explicit VARIADIC arguments correctly (Michael Paquier)
- Fix autovacuum's “work item” logic to prevent possible crashes and silent loss of work items (Álvaro Herrera)
- Fix corner-case crashes when columns have been added to the end of a view (Tom Lane)
- Record proper dependencies when a view or rule contains FieldSelect or FieldStore expression nodes (Tom Lane)
- Lack of these dependencies could allow a column or data type DROP to go through when it ought to fail, thereby causing later uses of the view or rule to get errorsThis patch does not do anything to protect existing views/rules, only ones created in the future.
- Correctly detect hashability of range data types (Tom Lane)
- The planner mistakenly assumed that any range type could be hashed for use in hash joins or hash aggregation, but actually it must check whether the range's subtype has hash supportThis does not affect any of the built-in range types, since they're all hashable anyway.
- Correctly ignore RelabelType expression nodes when examining functional-dependency statistics (David Rowley)
- This allows, e.g., extended statistics on varchar columns to be used properly.
- Prevent sharing transition states between ordered-set aggregates (David Rowley)
- This causes a crash with the built-in ordered-set aggregates, and probably with user-written ones as wellv11 and later will include provisions for dealing with such cases safely, but in released branches, just disable the optimization.
- Prevent idle_in_transaction_session_timeout from being ignored when a statement_timeout occurred earlier (Lukas Fittl)
- Fix low-probability loss of NOTIFY messages due to XID wraparound (Marko Tiikkaja, Tom Lane)
- If a session executed no queries, but merely listened for notifications, for more than 2 billion transactions, it started to miss some notifications from concurrently-committing transactions.
- Reduce the frequency of data flush requests during bulk file copies to avoid performance problems on macOS, particularly with its new APFS file system (Tom Lane)
- Allow COPY's FREEZE option to work when the transaction isolation level is REPEATABLE READ or higher (Noah Misch)
- This case was unintentionally broken by a previous bug fix.
- Fix AggGetAggref() to return the correct Aggref nodes to aggregate final functions whose transition calculations have been merged (Tom Lane)
- Fix insufficient schema-qualification in some new queries in pg_dump and psql (Vitaly Burovoy, Tom Lane, Noah Misch)
- Avoid use of @> operator in psql's queries for d (Tom Lane)
- This prevents problems when the parray_gin extension is installed, since that defines a conflicting operator.
- Fix pg_basebackup's matching of tablespace paths to canonicalize both paths before comparing (Michael Paquier)
- This is particularly helpful on Windows.
- Fix libpq to not require user's home directory to exist (Tom Lane)
- In v10, failure to find the home directory while trying to read ~/.pgpass was treated as a hard error, but it should just cause that file to not be foundBoth v10 and previous release branches made the same mistake when reading ~/.pg_service.conf, though this was less obvious since that file is not sought unless a service name is specified.
- In ecpglib, correctly handle backslashes in string literals depending on whether standard_conforming_strings is set (Tsunakawa Takayuki)
- Make ecpglib's Informix-compatibility mode ignore fractional digits in integer input strings, as expected (Gao Zengqi, Michael Meskes)
- Fix missing temp-install prerequisites for check-like Make targets (Noah Misch)
- Some non-default test procedures that are meant to work like make check failed to ensure that the temporary installation was up to date.
- Update time zone data files to tzdata release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus, Sudan, Tonga, and Turks & Caicos Islands, plus historical corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland, Namibia, and Pago Pago.
- In the documentation, restore HTML anchors to being upper-case strings (Peter Eisentraut)
- Due to a toolchain change, the 10.0 user manual had lower-case strings for intrapage anchors, thus breaking some external links into our website documentationReturn to our previous convention of using upper-case strings