Home 零对冲(ZeroHedge)每日HackerNews

PostgreSQL 18.7、17.12、16.16、15.20、14.25 和 19 RC 2 已发布
PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released

原始链接: https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/

PostgreSQL 全球开发组发布了所有支持版本（18.7、17.12、16.16、15.20、14.25）以及 PostgreSQL 19 RC2 的更新，修复了 52 个安全漏洞和 140+ 个 bug。PostgreSQL 14 现已终止支持。安全修复包括大量类型混淆、释放后使用、SQL 注入、权限绕过和任意代码执行问题。Bug 修复涵盖索引损坏（GIN、pg_trgm、B-tree）、表重写、规划器、逻辑复制、备份、psql 和时区数据。部分更新需要后续操作，如重建受影响的 GIN/GiST/B-tree 索引、修复分区表上的 NOT NULL NO INHERIT 约束，或创建新的完整/增量备份。PostgreSQL 19 RC2 预计于 2026 年 11 月 19 日正式发布，已列出 RC1 到 RC2 的修复内容。完整详情请参阅发行说明。

``` Hacker News 新 | 过去 | 评论 | 提问 | 展示 | 招聘 | 提交 登录 PostgreSQL 18.7、17.12、16.16、15.20、14.25 和 19 RC 2 已发布 ( postgresql.org ) 24 分 由 plaur782 1小时前 | 隐藏 | 过去 | 收藏 | 1 条评论 帮助 zulux 5分钟前 [–] 在我看来，像这样的大型补丁应被视为强制性补丁。如果在 LLM 风波的时代，我想把一次重大的安全更新推向实际应用，我就会这样做。 回复 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请加入 YC | 联系 搜索: ```
相关文章
原文

Posted on 2026-11-12 by PostgreSQL Global Development Group

PostgreSQL Project Security

The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 18.7, 17.12, 16.16, 15.20, and 14.25, as well as the second release candidate of PostgreSQL 19. This release fixes 52 security vulnerabilities and over 140 bugs reported over the last several months.

There are several issues that may require you to take extra steps after updating, which are described in detail below. See the "Updating" section for more information on post-update steps you may need to take.

For the full list of changes, please review the release notes.

PostgreSQL 14 EOL Notice

This is the final release of PostgreSQL 14. PostgreSQL 14 is now end-of-life and will no longer receive security and bug fixes. If you are running PostgreSQL 14 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.

Security Issues

The following security vulnerabilities are closed in this update release. You can find more details about the vulnerabilities and their affected versions in the links below:

  • CVE-2026-6460: Type confusion after ALTER ... SET DATA TYPE executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-6467: Extension script schema mishandling executes arbitrary SQL (CVSS v3.1: 7.2)
  • CVE-2026-14661: dblink and subscriptions can append to arbitrary files (CVSS v3.1: 8.1)
  • CVE-2026-16237: INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition (CVSS v3.1: 5.4)
  • CVE-2026-16240: pg_basebackup can use backup manifest content as a format string (CVSS v3.1: 3.7)
  • CVE-2026-18447: Output parameter type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116303: Foreign key and JSON conversions bypass EXECUTE privilege on cast functions (CVSS v3.1: 3.1)
  • CVE-2026-116304: Parallel RECORD typmod use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116306: Composite-type change during field assignment executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116307: plperl prepared-query use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116308: dict_int reads beyond zero-length tokens (CVSS v3.1: 4.3)
  • CVE-2026-116309: plperl blessed-reference type confusion may execute arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116310: COPY error context uses freed field storage (CVSS v3.1: 4.3)
  • CVE-2026-116311: DROP OWNED can remove restrictive row security policies from non-owned tables (CVSS v3.1: 5.4)
  • CVE-2026-116312: MERGE can place the wrong row in a trigger transition table (CVSS v3.1: 5.4)
  • CVE-2026-116313: vacuumdb --missing-stats-only lets a database owner execute code as the vacuumdb user (CVSS v3.1: 7.2)
  • CVE-2026-116314: pg_restore executes arbitrary code due to missing non-plain archive validation (CVSS v3.1: 8.8)
  • CVE-2026-116315: tsvector_delete() heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116316: Security-restricted operations can create types in pg_temp, which later queries of the session find (CVSS v3.1: 8.8)
  • CVE-2026-116317: ts_rank_cd() heap buffer overflow may execute arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116318: pg_dump not-null constraint name allows SQL injection (CVSS v3.1: 8.8)
  • CVE-2026-116319: plperl reentrant return_next() use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116320: plperl array and hash conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116321: Unterminated name value discloses server memory (CVSS v3.1: 4.3)
  • CVE-2026-116322: Pre-authentication cancel request can leak a spinlock (CVSS v3.1: 5.3)
  • CVE-2026-116323: pltcl reentrant result conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116325: reindexdb index name quoting allows SQL injection (CVSS v3.1: 8)
  • CVE-2026-116326: plperl tied-object exceptions follow stale sigjmp_buf (CVSS v3.1: 8.8)
  • CVE-2026-116327: security_barrier analysis can expose hidden values through indirect expressions (CVSS v3.1: 4.3)
  • CVE-2026-116328: Generation memory context integer wraparound executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116329: Statistics import type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116330: pg_dump tar restore.sql fails to block psql command injection (CVSS v3.1: 8.8)
  • CVE-2026-116331: Min/max aggregate type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116332: Portal setup use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116333: Parallel B-tree array scan reads beyond array bounds (CVSS v3.1: 6.5)
  • CVE-2026-116335: Commutator or negator result-type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-116336: REINDEX CONCURRENTLY does not block DROP INDEX during index functions (CVSS v3.1: 8.8)
  • CVE-2026-120139: Tuple-size integer wraparound executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120141: Materialized set-returning function type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120142: Dropped-column type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120143: Transition-table cursor use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120144: Type-cache invalidation gap executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120145: Logical replication can write to subscriber system catalogs, executing arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120146: REASSIGN OWNED bypasses role SET and CREATEDB checks (CVSS v3.1: 4.3)
  • CVE-2026-120147: dblink reentrant disconnect use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120148: Extended-statistics pseudo-type confusion executes arbitrary code (CVSS v3.1: 8.1)
  • CVE-2026-120149: FDW batch-insert mismatch executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120150: Expanded-record domain-check use-after-free executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120151: plpgsql record-field type confusion executes arbitrary code (CVSS v3.1: 8.8)
  • CVE-2026-120152: pg_show_all_settings() use-after-free discloses memory (CVSS v3.1: 4.3)
  • CVE-2026-120153: Extension-script substitutions allow SQL injection through object names (CVSS v3.1: 7.2)
  • CVE-2026-120154: INSERT ... ON CONFLICT can read rows despite row security policies (CVSS v3.1: 4.3)

Bug Fixes and Improvements

This update fixes over 140 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Many of these issues also affect other supported versions of PostgreSQL.

  • Fix exporting and importing snapshots taken on a standby server. The issue was detected when running a parallel pg_dump against a standby server, and could corrupt both the dump output and the standby server's data. More generally, a transaction that imported a snapshot taken on a standby server could return wrong results.
  • Several fixes for GIN indexes that could lead to index corruption, causing queries to miss rows or to return unrelated rows. If you suspect a GIN index is affected, you should reindex it. See the release notes for more details on the issue, and the "Updating" section for post-update steps.
  • Fix possible index corruption in pg_trgm GiST indexes that could cause searches to miss matching rows. You need to reindex after updating; see the "Updating" section.
  • Fix a case where, after REINDEX CONCURRENTLY rebuilt an index on a TOAST table, later index updates could be missed, leading to missing chunk number errors. If you've encountered this issue, after updating, you'll need to reindex. See the "Updating" section.
  • Disallow NOT NULL NO INHERIT constraints on partitioned tables in all cases, including CREATE TABLE ... LIKE. Previously, this could allow a partition to contain NULL values when it should not. See the "Updating" section for how to find and repair affected constraints.
  • Disable B-tree index deduplication for columns declared as bpchar without a length, which could cause index-only scans to return wrong results. If you have B-tree indexes on bpchar columns, you should reindex them after updating. See the "Updating" section.
  • Several fixes for incremental backups that could produce corrupt backups. We recommend taking a new full backup after updating and using it for subsequent incremental backups. See the "Updating" section.
  • Several fixes for base backups, including avoiding a torn copy of the pg_control file, and avoiding truncated or zero-padded copies of files such as postgresql.auto.conf that are replaced while the backup is running.
  • Rework the planner's join removal implementation. While this is a significant change for an update release, it was made to avoid continued bugs from the previous implementation.
  • Fix possible loss of rows during a table rewrite (for example, CLUSTER or VACUUM FULL) when a row had been updated by a subtransaction that later aborted.
  • Fix parallel vacuum I/O timing reports.
  • Several fixes that could cause data loss or inconsistency after a crash, including starting a checkpoint while creating a multixact or while aborting a prepared transaction. This release also writes the state files of pending prepared transactions atomically, as a crash could previously leave behind an invalid file that prevented the server from starting.
  • Several fixes to the planner that could produce wrong query results, including queries with LATERAL references, outer joins, self-join elimination on tables using inheritance, DISTINCT ON in a subquery with set-returning functions, and queries using non-deterministic collations.
  • Several fixes to partition pruning that could cause rows to be missed, including multi-column RANGE-partitioned tables when a query filters only on the leading columns, DEFAULT partitions on tables using MINVALUE or MAXVALUE bounds, and concurrent updates that could silently skip rows that should be updated.
  • Fix INSERT ... ON CONFLICT to acquire a predicate lock on the conflicting row under SERIALIZABLE isolation. Previously, concurrent updates that should have failed with a serialization error could succeed.
  • Fix MERGE with WHEN NOT MATCHED BY SOURCE when the target row is concurrently deleted. Previously, a WHEN NOT MATCHED BY TARGET action could run instead, giving incorrect results.
  • Several fixes for SQL/JSON functions such as JSON_TABLE and JSON_VALUE that could return incorrect results.
  • Several fixes for logical replication that could cause a subscriber to apply changes incorrectly.
  • Several fixes for standby servers, including avoiding unnecessary replay delays and query cancellations in certain cases.
  • Fix psql to accept multiple COPY ... FROM STDIN commands in a single command string. The fix for CVE-2026-6464 caused psql to reject these.
  • Several fixes that could cause a dump to fail to restore, or cause a restored view to behave differently from the original. These include views and rules that use AT TIME ZONE in a FROM clause or a target alias named set, tsvector and tsquery values that could fail to reload.
  • Fix the server becoming stuck, instead of exiting, if the startup process crashes while the server is restarting after a crash.

This release also updates time zone data files to tzdata release 2026f. Beginning in November 2026, Canada's Northwest Territories (America/Inuvik) are on year-round UTC-06 and Manitoba (America/Winnipeg) is on year-round UTC-05. This release assumes their TZ abbreviations will be CST and EST respectively (though this could change). It also reflects that Cuba will stay on daylight saving time this winter, and that the EST5EDT, CST6CDT, MST7MDT, and PST8PDT zone names now use their indicated UTC offsets for old timestamps instead of the history of their associated city-named zones.

Updating

All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply stop PostgreSQL and update its binaries.

If you suspect that a GIN index is affected by one of the corruption issues fixed in this release, you should reindex it, for example:

REINDEX INDEX your_index_name;

If you use pg_trgm, you should reindex any GiST indexes that use the gist_trgm_ops operator class.

If you see missing chunk number errors when reading a table, you should reindex the table, which also reindexes its TOAST table, for example:

REINDEX TABLE your_table_name;

If you use incremental backups, we recommend taking a new full backup after updating and using it as the basis for subsequent incremental backups.

If you use partitioned tables, the following query finds NOT NULL NO INHERIT constraints on partitioned tables:

SELECT conrelid::regclass, conname FROM pg_constraint WHERE contype = 'n' AND connoinherit AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');

You can remove unwanted constraints with ALTER TABLE ... DROP CONSTRAINT .... Constraints you want to keep should be repaired with ALTER TABLE ... ALTER CONSTRAINT ... INHERIT, which will fail if any of the table's partitions contain NULL values in that column.

If you have B-tree indexes on bpchar columns (that is, columns declared as bpchar without a length), you should reindex them after updating. Columns declared as char(n) are not affected.

Users who have skipped one or more update releases may need to run additional post-update steps; please see the release notes from earlier versions for details.

For more details, please see the release notes.

A Note on PostgreSQL 19 RC 2

This release marks the second release candidate of PostgreSQL 19. As a release candidate, PostgreSQL 19 RC 2 will be mostly identical to the initial release of PostgreSQL 19, though some more fixes may be applied prior to the general availability of PostgreSQL 19. PostgreSQL 19 RC 2 also includes the fixes in this update release that apply to PostgreSQL 19.

The planned date for the general availability of PostgreSQL 19 is November 19, 2026. Please see the "Release Schedule" section for more details.

Upgrading to PostgreSQL 19 RC 2

To upgrade to PostgreSQL 19 RC 2 from earlier versions of PostgreSQL, you will need to use a major version upgrade strategy, e.g. pg_upgrade or pg_dump / pg_restore. For more information, please visit the documentation section on upgrading:

https://www.postgresql.org/docs/19/upgrading.html

If you use pg_upgrade and have indexes that use full text search, pg_trgm, or fuzzystrmatch, please review the "Migration to Version 19" section of the release notes, as you may need to reindex them after upgrading.

Changes Since 19 RC 1

Several bug fixes were applied to PostgreSQL 19 during the RC 1 period. These include:

  • Revert a change that allowed JSON_ARRAY() and JSON_OBJECT() expressions over arrays, composite types, and range types to be used in expression indexes, generated columns, and partition keys, as these indexes could become out-of-date. If you created any of these objects while testing PostgreSQL 19, you need to drop or redefine them before upgrading, as pg_dump / pg_restore and pg_upgrade will fail to recreate them.
  • Fix wrong results in GROUPING SETS queries, where a column not included in the current grouping set could show a value instead of NULL.
  • Fix an infinite loop in first_value() and nth_value() when using IGNORE NULLS with some EXCLUDE frame options.
  • Fix eager aggregation running volatile functions in a join condition once per group instead of once per row.
  • Fix promotion of a standby server waiting indefinitely if a session is blocked sending data to a client that has stopped reading.
  • Fix the LISTEN / NOTIFY queue becoming stuck if a session is interrupted while reading notifications.
  • Fix foreign key checks that could fail with an error when the referencing column's type needs a cast to be compared with the referenced column.
  • Fix performance regressions in hash-based query execution, including hash tables that could be sized far beyond the work_mem limit based on the planner's row estimate.

For a detailed list of fixes, please visit the open items page.

Release Schedule

This is the second release candidate for PostgreSQL 19. Unless an issue is discovered that requires a delay or an additional release candidate, PostgreSQL 19 should be made generally available on November 19, 2026.

For further information please see the Beta Testing page.

Links

If you have corrections or suggestions for this release announcement, please send them to the [email protected] public mailing list.

联系我们 contact @ memedata.com