這是歷史版本頁面 — 看 PostgreSQL (32-bit) 最新版本

資料庫新手該選 PostgreSQL 嗎?它能幫你扛住什麼

PostgreSQL (32-bit) 軟體圖示 PostgreSQL (32-bit) 10.1 (32-bit) 資料更新 2017-11-10 閱讀約 9 分鐘

PostgreSQL 是一套開放原始碼的關聯式資料庫系統,當你開始寫程式、做專案,或公司內部要建一套正式的資料管理流程時,會發現 Excel 已經撐不住了——資料一多就卡、多人同時編輯就亂、想查個歷史紀錄得翻半天。你需要的是一個能穩定存放資料、讓程式隨時讀寫、而且不會動不動就壞掉的「資料倉庫」,PostgreSQL 就是被許多人拿來扮演這個角色的工具。

一般人直覺會先想到用 Excel 或 Access 頂著,但資料量一大、查詢一複雜,這些工具的極限很快就出現:檔案開不起來、公式跑不動、沒有辦法讓多個程式同時安全地存取。資料庫系統的切入點,是幫你把「資料的存放、查詢、權限、備份」這些事變成一套有規則的流程,讓程式可以透過標準的 SQL 語言跟它溝通,而不是靠人眼在表格裡找資料。

01PostgreSQL 到底能拿來做什麼?

它是關聯式資料庫管理系統,主要用途是存放結構化資料,例如會員帳號、訂單紀錄、庫存清單。你可以用 SQL 語法新增、查詢、修改、刪除資料,也能建立關聯表單來串接不同資料。它支援多種資料型態,包含數字、字串、日期、陣列、JSON,甚至地理座標。開發者常用它當作應用程式的後端資料庫,讓網站或桌面程式有地方穩定存資料。

02它跟 MySQL 或 SQLite 差在哪?我該怎麼選?

這三套都是資料庫,但定位不同。SQLite 是輕量級、單一檔案、適合小型專案或嵌入式裝置;MySQL 是常見的網頁資料庫,生態系龐大;PostgreSQL 則以功能完整著稱,支援較多進階功能,例如自訂資料型態、部分索引、序列化交易。如果你的需求是複雜查詢、大量資料、需要進階資料完整性控制,PostgreSQL 會是比較完整的選擇。但資料顯示,MySQL Workbench 和 SQLite 也有不少人使用,最終取決於你的專案規模和熟悉度。

03我完全沒用過資料庫,這套軟體學得會嗎?

可以,但需要花時間。PostgreSQL 本身是伺服器軟體,安裝後你會用 pgAdmin 圖形介面或命令列來操作。基本流程是:建立資料庫、建立資料表、用 SQL 下指令。SQL 是標準語言,網路上資源很多。它的官方文件寫得詳細,但都是英文。如果你第一次接觸資料庫,建議先從簡單的 SELECT、INSERT、UPDATE 開始,再慢慢學 JOIN 和索引。學習曲線比 SQLite 陡,但功能也強得多。

04它支援哪些程式語言?我寫 Python 或 Java 能用嗎?

可以。官方資料顯示 PostgreSQL 有原生的程式介面,支援 C/C++、Java、.Net、Perl、Python、Ruby、Tcl、ODBC 等。也就是說,你用 Python 的 psycopg2、Java 的 JDBC,或 .NET 的 Npgsql,都能連上它。連接方式通常是透過 PostgreSQL 相容的驅動程式,設定連線字串、帳號密碼,就能讓應用程式讀寫資料庫。這代表它很容易整合進現有的開發環境。

05資料量很大會不會跑不動?它有辦法處理百萬筆資料嗎?

官方資料提到表格大小可達 32 TB,並支援多種進階索引,如 B-tree、GiST、GIN、BRIN 等,還有查詢最佳化器、索引-only scans、多重欄位統計。這些功能是為了處理大量資料而設計的。實際效能取決於硬體、索引設計、查詢語法,但架構上是能應付大規模資料的。它也有表格分割(table partitioning)功能,可以把大表拆成小塊管理。不過官方也提到,需要手動調整效能,不是裝好就自動跑得快。

06什麼樣的人適合用 PostgreSQL?

適合需要「資料正確性」勝過「極致簡單」的人。例如你在開發商業應用、需要交易紀錄不能出錯、需要外鍵約束確保資料關聯正確、需要多使用者同時寫入而不衝突,這些都是它的強項。它也適合需要地理資訊(PostGIS)、JSON 文件處理、全文檢索的人。如果你只是要存幾百筆設定值,它會殺雞用牛刀。另外,它是開放原始碼、免費使用,對預算有限但需要正式資料庫的團隊很友善。

07我一個人開發小專案,用它會不會太複雜?

有可能。PostgreSQL 是完整的伺服器軟體,安裝後需要管理服務、設定帳號權限、處理備份。如果你只是做練習專案或 prototype,SQLite 只要一個檔案就能動,會輕鬆很多。PostgreSQL 的優勢在於多人協作、正式部署、資料量大時才明顯。如果你預期專案會長大、需要多人同時使用,那早點用 PostgreSQL 可以省去日後轉移的麻煩。但若只是暫時性的小工具,它的維護成本確實比較高。

08我習慣用圖形介面管理資料庫,這套有 GUI 嗎?

有,PostgreSQL 官方提供 pgAdmin,是圖形化管理工具,可以建立資料庫、下 SQL 查詢、管理使用者權限、看執行計畫。但官方資料也提到「內建的 GUI 管理工具有限」,意思是 pgAdmin 的功能不像商業資料庫的介面那麼完整,某些進階操作還是得用命令列。如果你習慣 MySQL Workbench 那種整合度高的介面,需要花點時間適應。另外,也有第三方工具可以連 PostgreSQL,但不在官方資料範圍內。

09我的電腦是 Windows 7,可以安裝嗎?

官方支援系統列的是 Windows 7 64 位元、Windows 8 64 位元、Windows 10 64 位元、Windows 11。所以如果你的 Windows 7 是 64 位元,理論上可以安裝。但要注意,官方也要求 64 位元處理器、至少 2GB 記憶體、100MB 安裝空間,以及 Microsoft Visual C++ Redistributable。如果你的系統是 32 位元,就無法安裝。另外,Windows 7 本身已停止支援,新版本 PostgreSQL 是否仍相容,需要自行確認。

10這套軟體有中文介面嗎?

官方資料顯示介面語系是英文。安裝程式、pgAdmin 介面、官方文件都是英文為主。雖然 PostgreSQL 支援國際字元集和 ICU 排序,但那是資料內容的編碼,不是操作介面。如果你英文閱讀有障礙,操作上會比較吃力。社群有中文討論區和教學文章,但官方工具本身沒有繁體中文介面。這點在選擇前要考慮進去。

11它需要付費嗎?開放原始碼是什麼意思?

它是 Open Source 授權,代表免費使用,也可以檢視、修改原始碼。官方資料強調「免費且開放原始碼」,所以不用付授權費。但免費不代表沒有成本——你需要花時間學習、設定、維護,硬體和人力成本還是要自己承擔。另外,雖然軟體本身免費,但如果你需要商業支援,得找第三方廠商,這部分官方資料沒有提供資訊。

12這套軟體是不是很少人用?社群活躍嗎?

官方資料顯示有 214 人評分,分數 7.98/10,更新頻繁——近 12 個月更新 10 次,代表開發團隊持續在維護。相比 MySQL Workbench 有 61 人評分、SQLite 有 95 人評分,PostgreSQL 的評分人數較多,但也不算極大量。它的社群和文件在資料庫圈內是公認的完整,但你要能讀英文。如果你需要中文資源,得靠論壇或部落格補足。整體來說,它不是冷門軟體,但也不是最多人用的那一套。

13什麼情況不該選 PostgreSQL?

如果你只需要一個簡單的資料儲存方案,例如單機應用程式、幾千筆資料、不需要多人同時連線,SQLite 更輕量。如果你需要微軟生態系的深度整合,SQL Server 可能更合適,但這不在官方比較清單中。如果你完全不想碰命令列、只想要圖形介面點一點就完成所有操作,PostgreSQL 的內建 GUI 工具會讓你有挫折感。另外,如果你的作業系統是 32 位元,或記憶體只有 2GB 以下,跑起來會很吃力。最後,如果你需要中文介面,它目前不提供。

下載與官方連結

前往官方網站 下載 PostgreSQL (32-bit)

postgresql-10.1-1-windows.exe · 連結指向軟體原廠

版本紀錄

再看 5 筆

看完整版本清單

這一版改了什麼

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