PostgreSQL 9.4.5

PostgreSQL 是一款強大的開源關聯式資料庫系統，旨在提供可靠且正確的資料儲存解決方案。它支援絕大多數的 SQL 資料型別以及圖片、聲音與影像等二進位資料，並提供多種原生程式設計介面供開發者調用。由於其架構經過嚴格驗證且長期維護，在同類工具中屬於主流首選，是追求穩定性與功能強大的免費資料庫方案。

這套軟體適合需要自行架設網站的中小企業或軟體開發者，尤其在對系統記憶體佔用較敏感的情境下非常實用。相較於部分針對特定功能收費的替代方案，PostgreSQL 提供了極具競爭力的開源選擇。使用者在下載前需留意其主要支援英文語系，且可運行於 Windows、macOS 及 Linux 等多數主流作業系統。

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 上？（更多資訊）

- Guard against stack overflows in json parsing
> If an application constructs PostgreSQL json or jsonb values from arbitrary user input, the application's users can reliably crash the PostgreSQL server, causing momentary denial of service.
- Fix contrib/pgcrypto to detect and report too-short crypt() salts
> Certain invalid salt arguments crashed the server or disclosed a few bytes of server memory. We have not ruled out the viability of attacks that arrange for presence of confidential information in the disclosed bytes, but they seem unlikely.
- Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails
> A function executed in an outer-subtransaction cursor could cause an assertion failure or crash by referencing a relation created within an inner subtransaction.
- Fix possible deadlock during WAL insertion when commit_delay is set
- Ensure all relations referred to by an updatable view are properly locked during an update statement
- Fix insertion of relations into the relation cache "init file"
> An oversight in a patch in the most recent minor releases caused pg_trigger_tgrelid_tgname_index to be omitted from the init file. Subsequent sessions detected this, then deemed the init file to be broken and silently ignored it, resulting in a significant degradation in session startup time. In addition to fixing the bug, install some guards so that any similar future mistake will be more obvious.
- Avoid O(N^2) behavior when inserting many tuples into a SPI query result
- Improve LISTEN startup time when there are many unread notifications
- Fix performance problem when a session alters large numbers of foreign key constraints
> This was seen primarily when restoring pg_dump output for databases with many thousands of tables.
- Disable SSL renegotiation by default
> While use of SSL renegotiation is a good idea in theory, we have seen too many bugs in practice, both in the underlying OpenSSL library and in our usage of it. Renegotiation will be removed entirely in 9.5 and later. In the older branches, just change the default value of ssl_renegotiation_limit to zero (disabled).
- Lower the minimum values of the *_freeze_max_age parameters
> This is mainly to make tests of related behavior less time-consuming, but it may also be of value for installations with limited disk space.
- Limit the maximum value of wal_buffers to 2GB to avoid server crashes
- Avoid logging complaints when a parameter that can only be set at server start appears multiple times in postgresql.conf, and fix counting of line numbers after an include_dir directive
- Fix rare internal overflow in multiplication of numeric values
- Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int
- Fix handling of DOW and DOY in datetime input
> These tokens aren't meant to be used in datetime values, but previously they resulted in opaque internal error messages rather than "invalid input syntax".
- Add more query-cancel checks to regular expression matching
- Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching
> Suitable search patterns and a low stack depth limit could lead to stack-overrun crashes.
- Fix potential infinite loop in regular expression execution
> A search pattern that can apparently match a zero-length string, but actually doesn't match because of a back reference, could lead to an infinite loop.
- In regular expression execution, correctly record match data for capturing parentheses within a quantifier even when the match is zero-length
- Fix low-memory failures in regular expression compilation
- Fix low-probability memory leak during regular expression execution
- Fix rare low-memory failure in lock cleanup during transaction abort
- Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings
- Fix very-low-probability stack overrun in qsort
- Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings
- Fix assorted planner bugs
> These mistakes could lead to incorrect query plans that would give wrong answers, or to assertion failures in assert-enabled builds, or to odd planner errors such as "could not devise a query plan for the given query", "could not find pathkey item to sort", "plan should not reference subplan's variable", or "failed to assign all NestLoopParams to plan nodes". Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz testing that exposed these problems.
- Improve planner's performance for UPDATE/DELETE on large inheritance sets -
- Ensure standby promotion trigger files are removed at postmaster startup
- This prevents unwanted promotion from occurring if these files appear in a database backup that is used to initialize a new standby server.
- During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file
> This avoids race-condition failures if an external script attempts to start a new postmaster as soon as pg_ctl stop returns.
- Ensure that the postmaster does not exit until all its child processes are gone, even in an immediate shutdown
> Like the previous item, this avoids possible race conditions against a subsequently-started postmaster.
- Fix postmaster's handling of a startup-process crash during crash recovery
> If, during a crash recovery cycle, the startup process crashes without having restored database consistency, we'd try to launch a new startup process, which typically would just crash again, leading to an infinite loop.
- Make emergency autovacuuming for multixact wraparound more robust
- Do not print a WARNING when an autovacuum worker is already gone when we attempt to signal it, and reduce log verbosity for such signals
- Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount
- Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests
- Allow all-zeroes pages in GIN indexes to be reused
> Such a page might be left behind after a crash.
- Fix handling of all-zeroes pages in SP-GiST indexes
> VACUUM attempted to recycle such pages, but did so in a way that wasn't crash-safe.
- Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation
- Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages
- Fix PL/Perl to handle non-ASCII error message texts correctly
- Fix PL/Python crash when returning the string representation of a record result
- Fix some places in PL/Tcl that neglected to check for failure of malloc() calls
- In contrib/isn, fix output of ISBN-13 numbers that begin with 979
> EANs beginning with 979 (but not 9790) are considered ISBNs, but they must be printed in the new 13-digit format, not the 10-digit format.
- Improve contrib/pg_stat_statements' handling of query-text garbage collection
> The external file containing query texts could bloat to very large sizes; once it got past 1GB attempts to trim it would fail, soon leading to situations where the file could not be read at all.
- Improve contrib/postgres_fdw's handling of collation-related decisions
> The main user-visible effect is expected to be that comparisons involving varchar columns will be sent to the remote server for execution in more cases than before.
- Improve libpq's handling of out-of-memory conditions
- Fix memory leaks and missing out-of-memory checks in ecpg
- Fix psql's code for locale-aware formatting of numeric output
> The formatting code invoked by pset numericlocale on did the wrong thing for some uncommon cases such as numbers with an exponent but no decimal point. It could also mangle already-localized output from the money data type.
- Prevent crash in psql's c command when there is no current connection
- Make pg_dump handle inherited NOT VALID check constraints correctly
- Fix selection of default zlib compression level in pg_dump's directory output format
- Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable
- Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace
- Fix pg_dump to handle object privileges sanely when dumping from a server too old to have a particular privilege type
> When dumping data types from pre-9.2 servers, and when dumping functions or procedural languages from pre-7.3 servers, pg_dump would produce GRANT/REVOKE commands that revoked the owner's grantable privileges and instead granted all privileges to PUBLIC. Since the privileges involved are just USAGE and EXECUTE, this isn't a security problem, but it's certainly a surprising representation of the older systems' behavior. Fix it to leave the default privilege state alone in these cases.
- Fix pg_dump to dump shell types
> Shell types (that is, not-yet-fully-defined types) aren't useful for much, but nonetheless pg_dump should dump them.
- Fix assorted minor memory leaks in pg_dump and other client-side programs
- Fix pgbench's progress-report behavior when a query, or pgbench itself, gets stuck
- Fix spinlock assembly code for Alpha hardware
- Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler
> Building with gcc didn't work if gcc had been configured to use the native assembler, which is becoming more common.
- On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use
- On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime
> Perl relies on this ability in 5.8.0 and later.
- Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs
- Use librt for sched_yield() when necessary, which it is on some Solaris versions
- Translate encoding UHC as Windows code page 949
> This fixes presentation of non-ASCII log messages from processes that are not attached to any particular database, such as the postmaster.
- On Windows, avoid failure when doing encoding conversion to UTF16 outside a transaction, such as for log messages
- Fix postmaster startup failure due to not copying setlocale()'s return value
> This has been reported on Windows systems with the ANSI code page set to CP936 ("Chinese (Simplified, PRC)"), and may occur with other multibyte code pages.
- Fix Windows install.bat script to handle target directory names that contain spaces
- Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM
- Update time zone data files to tzdata release 2015g for DST law changes in Cayman Islands, Fiji, Moldova, Morocco, Norfolk Island, North Korea, Turkey, and Uruguay. There is a new zone name America/Fort_Nelson for the Canadian Northern Rockies.