PostgreSQL 9.0.4

PostgreSQL 是一款功能強大、開放原始碼的物件關聯式資料庫系統。它歷經超過 15 年的積極開發，其成熟的架構為可靠性、資料完整性與正確性贏得了良好聲譽。

它可在所有主流作業系統上執行，包括 Linux、UNIX（AIX、BSD、HP-UX、SGI IRIX、macOS、Solaris、Tru64）以及 Windows。PostgreSQL 是一款強大的物件關聯式資料庫管理系統！下載適用於 PC 的 PostgreSQL 離線安裝程式 64 位元版本！

它完全符合 ACID 規範，並完整支援外部鍵、聯結、檢視、觸發器以及預存程序（支援多種語言）。它包含大多數 SQL:2008 資料型別，包括 INTEGER、NUMERIC、BOOLEAN、CHAR、VARCHAR、DATE、INTERVAL 和 TIMESTAMP。

它也支援儲存二進位大型物件，包括圖片、音訊或影片。它具備 C/C++、Java、.Net、Perl、Python、Ruby、Tcl、ODBC 等原生程式設計介面，並提供卓越的文件（資料表大小最高可達 32 TB）。

PostgreSQL 2026 具備許多功能，旨在協助開發人員建置應用程式、協助管理員保護資料完整性並建置容錯環境，同時協助您管理任何規模的資料集。除了免費且開放原始碼之外，這款工具還具有高度擴充性。

例如，您可以定義自己的資料型別、建立自訂函式，甚至使用不同的程式語言撰寫程式碼，而無需重新編譯資料庫！

此應用程式力求在符合 SQL 標準的同時，不與傳統功能牴觸，也不會導致不良的架構決策。

SQL 標準要求的許多功能都已支援，不過有時語法或功能會略有差異。未來可望進一步提升標準符合度。

功能與重點

資料型別

• 基本型別：整數、數值、字串、布林值
• 結構化：日期/時間、陣列、範圍、UUID
• 文件型別：JSON/JSONB、XML、鍵值對（Hstore）
• 幾何型別：點、線、圓、多邊形
• 自訂：複合型別、自訂型別

資料完整性

• UNIQUE、NOT NULL
• 主鍵
• 外部鍵
• 排除約束
• 明確鎖定、建議鎖定

並行性與效能

• 索引：B-tree、多欄位、運算式、部分索引
• 進階索引：GiST、SP-GiST、KNN GiST、GIN、BRIN、涵蓋索引、布隆過濾器
• 精密的查詢規劃器/最佳化器、僅索引掃描、多欄位統計
• 交易、巢狀交易（透過儲存點）
• 多版本並行控制（MVCC）
• 讀取查詢與建立 B-tree 索引的平行化
• 資料表分割
• SQL 標準定義的所有交易隔離層級，包括可序列化
• 運算式的即時（JIT）編譯

可靠性與災難復原

• 預寫式記錄（WAL）
• 複寫：非同步、同步、邏輯
• 時間點復原（PITR）、主動備援
• 資料表空間

安全性

• 驗證：GSSAPI、SSPI、LDAP、SCRAM-SHA-256、憑證等
• 健全的存取控制系統
• 欄位與列層級安全性

擴充性

• 預存函式與程序
• 程序語言：PL/pgSQL、Perl、Python（以及更多）
• 外部資料包裝器：透過標準 SQL 介面連線至其他資料庫或串流
• 許多提供額外功能的擴充套件，包括 PostGIS

國際化與全文檢索

• 支援國際字元集，例如透過 ICU 定序
• 全文檢索

使用方式

• 從官方網站或 FileHorse.com 下載並安裝此程式
• 開啟 pgAdmin 或使用命令列進行資料庫管理
• 使用 pgAdmin 介面建立新資料庫
• 使用 SQL 查詢來建立、讀取、更新和刪除資料
• 設定使用者角色與權限以確保安全性
• 使用 pgAdmin 或命令列備份與還原資料庫
• 使用索引與查詢調校來最佳化效能
• 使用 PostgreSQL 相容驅動程式連線應用程式
• 使用內建記錄工具監控資料庫活動
• 保持 PostgreSQL 更新以確保安全性與效能

系統需求

作業系統：Windows 11 或 Windows 10（64 位元）

處理器：Intel 或 AMD 64 位元處理器

記憶體：最低 2GB，建議 4GB 或以上

儲存空間：安裝至少需要 100MB，資料儲存另需更多空間

其他需求：需要 Microsoft Visual C++ 可轉散發套件

優點

• 開放原始碼且免費使用
• 進階安全性功能
• 高擴充性與效能
• 支援複雜查詢與索引
• 強大的社群與文件

缺點

• 需要手動效能調校
• 某些情況下記憶體使用量較高
• 內建 GUI 管理工具有限
• 升級可能需要手動調整

另有提供：下載 PostgreSQL for Mac

下載 PostgreSQL 最新版本 為什麼此應用程式發佈在 FileHorse 上？（更多資訊）

* Fix pg_upgrade's handling of TOAST tables
The pg_class.relfrozenxid value for TOAST tables was not correctly copied into the new installation during pg_upgrade. This could later result in pg_clog files being discarded while they were still needed to validate tuples in the TOAST tables, leading to "could not access status of transaction" failures.
This error poses a significant risk of data loss for installations that have been upgraded with pg_upgrade. This patch corrects the problem for future uses of pg_upgrade, but does not in itself cure the issue in installations that have been processed with a buggy version of pg_upgrade.
* Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set" warning
VACUUM would sometimes issue this warning in cases that are actually valid.
* Use better SQLSTATE error codes for hot standby conflict cases
All retryable conflict errors now have an error code that indicates that a retry is possible. Also, session closure due to the database being dropped on the master is now reported as ERRCODE_DATABASE_DROPPED, rather than ERRCODE_ADMIN_SHUTDOWN, so that connection poolers can handle the situation correctly.
* Prevent intermittent hang in interactions of startup process with bgwriter process
This affected recovery in non-hot-standby cases.
* Disallow including a composite type in itself
This prevents scenarios wherein the server could recurse infinitely while processing the composite type. While there are some possible uses for such a structure, they don't seem compelling enough to justify the effort required to make sure it always works safely.
* Avoid potential deadlock during catalog cache initialization
In some cases the cache loading code would acquire share lock on a system index before locking the index's catalog. This could deadlock against processes trying to acquire exclusive locks in the other, more standard order.
* Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling when there was a concurrent update to the target tuple
This bug has been observed to result in intermittent "cannot extract system attribute from virtual tuple" failures while trying to do UPDATE RETURNING ctid. There is a very small probability of more serious errors, such as generating incorrect index entries for the updated tuple.
* Disallow DROP TABLE when there are pending deferred trigger events for the table
Formerly the DROP would go through, leading to "could not open relation with OID nnn" errors when the triggers were eventually fired.
* Allow "replication" as a user name in pg_hba.conf
"replication" is special in the database name column, but it was mistakenly also treated as special in the user name column.
* Prevent crash triggered by constant-false WHERE conditions during GEQO optimization
* Improve planner's handling of semi-join and anti-join cases
* Fix handling of SELECT FOR UPDATE in a sub-SELECT
This bug typically led to "cannot extract system attribute from virtual tuple" errors.
* Fix selectivity estimation for text search to account for NULLs
* Fix get_actual_variable_range() to support hypothetical indexes injected by an index adviser plugin
* Fix PL/Python memory leak involving array slices
* Allow libpq's SSL initialization to succeed when user's home directory is unavailable
If the SSL mode is such that a root certificate file is not required, there is no need to fail. This change restores the behavior to what it was in pre-9.0 releases.
* Fix libpq to return a useful error message for errors detected in conninfo_array_parse
A typo caused the library to return NULL, rather than the PGconn structure containing the error message, to the application.
* Fix ecpg preprocessor's handling of float constants
* Fix parallel pg_restore to handle comments on POST_DATA items correctly
* Fix pg_restore to cope with long lines (over 1KB) in TOC files
* Put in more safeguards against crashing due to division-by-zero with overly enthusiastic compiler optimization
* Support use of dlopen() in FreeBSD and OpenBSD on MIPS
There was a hard-wired assumption that this system function was not available on MIPS hardware on these systems. Use a compile-time test instead, since more recent versions have it.
* Fix compilation failures on HP-UX
* Avoid crash when trying to write to the Windows console very early in process startup
* Support building with MinGW 64 bit compiler for Windows
* Fix version-incompatibility problem with libintl on Windows
* Fix usage of xcopy in Windows build scripts to work correctly under Windows 7
This affects the build scripts only, not installation or usage.
* Fix path separator used by pg_regress on Cygwin
* Update time zone data files to tzdata release 2011f for DST law changes in Chile, Cuba, Falkland Islands, Morocco, Samoa, and Turkey; also historical corrections for South Australia, Alaska, and Hawaii.