{"article":{"slug":"postgresql-18-7-17-12-16-16-15-20-14-25-and-19-rc-2-released","title":"PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released!","subtitle":null,"summary":"The PostgreSQL Global Development Group released updates to all supported versions plus PostgreSQL 19 RC 2, fixing 52 security vulnerabilities and over 140 bugs; it is also the final release of PostgreSQL 14, which is now end-of-life.","content_type":"changelog","language":"en","canonical_url":"https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/","author":{"name":"PostgreSQL Global Development Group","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"PostgreSQL","url":"https://www.postgresql.org/","listing_slug":null,"listing":null},"topics":[{"name":"databases","slug":"databases","url":"https://listedarticles.com/topics/databases"},{"name":"security","slug":"security","url":"https://listedarticles.com/topics/security"},{"name":"open-source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"announcements","slug":"announcements","url":"https://listedarticles.com/topics/announcements"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":2516,"reading_minutes":11,"published_at":"2026-11-12T00:00:00.000Z","added_at":"2026-11-12T20:12:04.554Z","updated_at":"2026-11-12T20:12:04.554Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/postgresql-18-7-17-12-16-16-15-20-14-25-and-19-rc-2-released","markdown_url":"https://listedarticles.com/articles/postgresql-18-7-17-12-16-16-15-20-14-25-and-19-rc-2-released.md","example":false,"citation":"PostgreSQL Global Development Group, PostgreSQL. \"PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released!.\" 12 Nov 2026. https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/ (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/"},"body_markdown":"# PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released!\n\nPosted on **2026-11-12** by PostgreSQL Global Development Group\n\nPostgreSQL Project\n Security\n\nThe PostgreSQL Global Development Group has released an update to all\nsupported versions of PostgreSQL, including 18.7, 17.12, 16.16, 15.20, and\n14.25, as well as the second release candidate of PostgreSQL 19. This release\nfixes 52 security vulnerabilities and over 140 bugs reported over the last\nseveral months.\n\nThere are several issues that may require you to take extra steps after\nupdating, which are described in detail below. See the \"Updating\" section for\nmore information on post-update steps you may need to take.\n\nFor the full list of changes, please review the [release\nnotes](https://www.postgresql.org/docs/release/).\n\n## PostgreSQL 14 EOL Notice\n\n**This is the final release of PostgreSQL 14**. PostgreSQL 14 is now end-of-life\nand will no longer receive security and bug fixes. If you are running\nPostgreSQL 14 in a production environment, we suggest that you make plans to\nupgrade to a newer, supported version of PostgreSQL. Please see our\n[versioning policy](https://www.postgresql.org/support/versioning/) for more\ninformation.\n\n## Security Issues\n\nThe following security vulnerabilities are closed in this update release.\nYou can find more details about the vulnerabilities and their affected versions\nin the links below:\n\n- [CVE-2026-6460](https://www.postgresql.org/support/security/CVE-2026-6460/): Type confusion after `ALTER ... SET DATA TYPE` executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-6467](https://www.postgresql.org/support/security/CVE-2026-6467/): Extension script schema mishandling executes arbitrary SQL (CVSS v3.1: [7.2](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-14661](https://www.postgresql.org/support/security/CVE-2026-14661/): `dblink` and subscriptions can append to arbitrary files (CVSS v3.1: [8.1](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H))\n- [CVE-2026-16237](https://www.postgresql.org/support/security/CVE-2026-16237/): `INSERT ... ON CONFLICT` can read or modify rows despite auto-updatable view `WHERE` condition (CVSS v3.1: [5.4](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N))\n- [CVE-2026-16240](https://www.postgresql.org/support/security/CVE-2026-16240/): `pg_basebackup` can use backup manifest content as a format string (CVSS v3.1: [3.7](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-18447](https://www.postgresql.org/support/security/CVE-2026-18447/): Output parameter type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116303](https://www.postgresql.org/support/security/CVE-2026-116303/): Foreign key and JSON conversions bypass `EXECUTE` privilege on cast functions (CVSS v3.1: [3.1](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-116304](https://www.postgresql.org/support/security/CVE-2026-116304/): Parallel `RECORD` typmod use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116306](https://www.postgresql.org/support/security/CVE-2026-116306/): Composite-type change during field assignment executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116307](https://www.postgresql.org/support/security/CVE-2026-116307/): `plperl` prepared-query use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116308](https://www.postgresql.org/support/security/CVE-2026-116308/): `dict_int` reads beyond zero-length tokens (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-116309](https://www.postgresql.org/support/security/CVE-2026-116309/): `plperl` blessed-reference type confusion may execute arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116310](https://www.postgresql.org/support/security/CVE-2026-116310/): `COPY` error context uses freed field storage (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-116311](https://www.postgresql.org/support/security/CVE-2026-116311/): `DROP OWNED` can remove restrictive row security policies from non-owned tables (CVSS v3.1: [5.4](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N))\n- [CVE-2026-116312](https://www.postgresql.org/support/security/CVE-2026-116312/): `MERGE` can place the wrong row in a trigger transition table (CVSS v3.1: [5.4](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N))\n- [CVE-2026-116313](https://www.postgresql.org/support/security/CVE-2026-116313/): `vacuumdb --missing-stats-only` lets a database owner execute code as the `vacuumdb` user (CVSS v3.1: [7.2](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116314](https://www.postgresql.org/support/security/CVE-2026-116314/): `pg_restore` executes arbitrary code due to missing non-plain archive validation (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H))\n- [CVE-2026-116315](https://www.postgresql.org/support/security/CVE-2026-116315/): `tsvector_delete()` heap buffer overflow executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116316](https://www.postgresql.org/support/security/CVE-2026-116316/): Security-restricted operations can create types in pg\\_temp, which later queries of the session find (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116317](https://www.postgresql.org/support/security/CVE-2026-116317/): `ts_rank_cd()` heap buffer overflow may execute arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116318](https://www.postgresql.org/support/security/CVE-2026-116318/): `pg_dump` not-null constraint name allows SQL injection (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116319](https://www.postgresql.org/support/security/CVE-2026-116319/): `plperl` reentrant `return_next()` use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116320](https://www.postgresql.org/support/security/CVE-2026-116320/): `plperl` array and hash conversion use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116321](https://www.postgresql.org/support/security/CVE-2026-116321/): Unterminated name value discloses server memory (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-116322](https://www.postgresql.org/support/security/CVE-2026-116322/): Pre-authentication cancel request can leak a spinlock (CVSS v3.1: [5.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L))\n- [CVE-2026-116323](https://www.postgresql.org/support/security/CVE-2026-116323/): `pltcl` reentrant result conversion use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116325](https://www.postgresql.org/support/security/CVE-2026-116325/): `reindexdb` index name quoting allows SQL injection (CVSS v3.1: [8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H))\n- [CVE-2026-116326](https://www.postgresql.org/support/security/CVE-2026-116326/): `plperl` tied-object exceptions follow stale sigjmp\\_buf (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116327](https://www.postgresql.org/support/security/CVE-2026-116327/): `security_barrier` analysis can expose hidden values through indirect expressions (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-116328](https://www.postgresql.org/support/security/CVE-2026-116328/): Generation memory context integer wraparound executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116329](https://www.postgresql.org/support/security/CVE-2026-116329/): Statistics import type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116330](https://www.postgresql.org/support/security/CVE-2026-116330/): `pg_dump` tar restore.sql fails to block psql command injection (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H))\n- [CVE-2026-116331](https://www.postgresql.org/support/security/CVE-2026-116331/): Min/max aggregate type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116332](https://www.postgresql.org/support/security/CVE-2026-116332/): Portal setup use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116333](https://www.postgresql.org/support/security/CVE-2026-116333/): Parallel B-tree array scan reads beyond array bounds (CVSS v3.1: [6.5](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N))\n- [CVE-2026-116335](https://www.postgresql.org/support/security/CVE-2026-116335/): Commutator or negator result-type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-116336](https://www.postgresql.org/support/security/CVE-2026-116336/): `REINDEX CONCURRENTLY` does not block `DROP INDEX` during index functions (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120139](https://www.postgresql.org/support/security/CVE-2026-120139/): Tuple-size integer wraparound executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120141](https://www.postgresql.org/support/security/CVE-2026-120141/): Materialized set-returning function type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120142](https://www.postgresql.org/support/security/CVE-2026-120142/): Dropped-column type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120143](https://www.postgresql.org/support/security/CVE-2026-120143/): Transition-table cursor use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120144](https://www.postgresql.org/support/security/CVE-2026-120144/): Type-cache invalidation gap executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120145](https://www.postgresql.org/support/security/CVE-2026-120145/): Logical replication can write to subscriber system catalogs, executing arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H))\n- [CVE-2026-120146](https://www.postgresql.org/support/security/CVE-2026-120146/): `REASSIGN OWNED` bypasses role `SET` and `CREATEDB` checks (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N))\n- [CVE-2026-120147](https://www.postgresql.org/support/security/CVE-2026-120147/): `dblink` reentrant disconnect use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120148](https://www.postgresql.org/support/security/CVE-2026-120148/): Extended-statistics pseudo-type confusion executes arbitrary code (CVSS v3.1: [8.1](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N))\n- [CVE-2026-120149](https://www.postgresql.org/support/security/CVE-2026-120149/): FDW batch-insert mismatch executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120150](https://www.postgresql.org/support/security/CVE-2026-120150/): Expanded-record domain-check use-after-free executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120151](https://www.postgresql.org/support/security/CVE-2026-120151/): `plpgsql` record-field type confusion executes arbitrary code (CVSS v3.1: [8.8](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120152](https://www.postgresql.org/support/security/CVE-2026-120152/): `pg_show_all_settings()` use-after-free discloses memory (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n- [CVE-2026-120153](https://www.postgresql.org/support/security/CVE-2026-120153/): Extension-script substitutions allow SQL injection through object names (CVSS v3.1: [7.2](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H))\n- [CVE-2026-120154](https://www.postgresql.org/support/security/CVE-2026-120154/): `INSERT ... ON CONFLICT` can read rows despite row security policies (CVSS v3.1: [4.3](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N))\n\n## Bug Fixes and Improvements\n\nThis update fixes over 140 bugs that were reported in the last several\nmonths. The issues listed below affect PostgreSQL 18. Many of these issues\nalso affect other supported versions of PostgreSQL.\n\n- Fix exporting and importing\n  [snapshots](https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-SNAPSHOT-SYNCHRONIZATION)\n  taken on a standby server. The issue was detected when running a parallel\n  [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html) against a\n  standby server, and could corrupt both the dump output and the standby server's\n  data. More generally, a transaction that imported a snapshot taken on a standby\n  server could return wrong results.\n- Several fixes for [GIN](https://www.postgresql.org/docs/current/gin.html)\n  indexes that could lead to index corruption, causing queries to miss rows or to\n  return unrelated rows. If you suspect a GIN index is affected, you should\n  reindex it. See the release notes for more details on the issue, and\n  the \"Updating\" section for post-update steps.\n- Fix possible index corruption in\n  [`pg_trgm`](https://www.postgresql.org/docs/current/pgtrgm.html) GiST indexes\n  that could cause searches to miss matching rows. You need to reindex after\n  updating; see the \"Updating\" section.\n- Fix a case where, after\n  [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html)\n  rebuilt an index on a\n  [TOAST](https://www.postgresql.org/docs/current/storage-toast.html) table,\n  later index updates could be missed, leading to `missing chunk number` errors.\n  If you've encountered this issue, after updating, you'll need to reindex. See\n  the \"Updating\" section.\n- Disallow `NOT NULL NO INHERIT` constraints on partitioned tables in all\n  cases, including `CREATE TABLE ... LIKE`. Previously, this could allow a\n  partition to contain `NULL` values when it should not. See the \"Updating\"\n  section for how to find and repair affected constraints.\n- Disable B-tree index deduplication for columns declared as `bpchar` without a\n  length, which could cause index-only scans to return wrong results. If you have\n  B-tree indexes on `bpchar` columns, you should reindex them after updating. See\n  the \"Updating\" section.\n- Several fixes for incremental backups that could produce corrupt backups. We\n  recommend taking a new full backup after updating and using it for subsequent\n  incremental backups. See the \"Updating\" section.\n- Several fixes for\n  [base backups](https://www.postgresql.org/docs/current/app-pgbasebackup.html),\n  including avoiding a torn copy of the `pg_control` file, and avoiding\n  truncated or zero-padded copies of files such as `postgresql.auto.conf` that\n  are replaced while the backup is running.\n- Rework the planner's join removal implementation. While this is a significant\n  change for an update release, it was made to avoid continued bugs from the\n  previous implementation.\n- Fix possible loss of rows during a table rewrite (for example,\n  [`CLUSTER`](https://www.postgresql.org/docs/current/sql-cluster.html) or\n  `VACUUM FULL`) when a row had been updated by a subtransaction that later\n  aborted.\n- Fix parallel vacuum I/O timing reports.\n- Several fixes that could cause data loss or inconsistency after a crash,\n  including starting a checkpoint while creating a multixact or while aborting a\n  [prepared transaction](https://www.postgresql.org/docs/current/sql-prepare-transaction.html).\n  This release also writes the state files of pending prepared transactions\n  atomically, as a crash could previously leave behind an invalid file that\n  prevented the server from starting.\n- Several fixes to the planner that could produce wrong query results,\n  including queries with `LATERAL` references, outer joins, self-join elimination\n  on tables using inheritance, `DISTINCT ON` in a subquery with set-returning\n  functions, and queries using non-deterministic collations.\n- Several fixes to [partition\n  pruning](https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITION-PRUNING)\n  that could cause rows to be missed, including multi-column `RANGE`-partitioned\n  tables when a query filters only on the leading columns, `DEFAULT` partitions\n  on tables using `MINVALUE` or `MAXVALUE` bounds, and concurrent updates that\n  could silently skip rows that should be updated.\n- Fix [`INSERT ... ON\n  CONFLICT`](https://www.postgresql.org/docs/current/sql-insert.html#SQL-ON-CONFLICT)\n  to acquire a predicate lock on the conflicting row under\n  [`SERIALIZABLE`](https://www.postgresql.org/docs/current/transaction-iso.html#XACT-SERIALIZABLE)\n  isolation. Previously, concurrent updates that should have failed with a\n  serialization error could succeed.\n- Fix [`MERGE`](https://www.postgresql.org/docs/current/sql-merge.html) with\n  `WHEN NOT MATCHED BY SOURCE` when the target row is concurrently deleted.\n  Previously, a `WHEN NOT MATCHED BY TARGET` action could run instead, giving\n  incorrect results.\n- Several fixes for\n  [SQL/JSON](https://www.postgresql.org/docs/current/functions-json.html)\n  functions such as `JSON_TABLE` and `JSON_VALUE` that could return incorrect\n  results.\n- Several fixes for [logical\n  replication](https://www.postgresql.org/docs/current/logical-replication.html)\n  that could cause a subscriber to apply changes incorrectly.\n- Several fixes for [standby\n  servers](https://www.postgresql.org/docs/current/hot-standby.html), including\n  avoiding unnecessary replay delays and query cancellations in certain cases.\n- Fix [`psql`](https://www.postgresql.org/docs/current/app-psql.html) to accept\n  multiple [`COPY ... FROM STDIN`](https://www.postgresql.org/docs/current/sql-copy.html)\n  commands in a single command string. The fix for [CVE-2026-6464](https://www.postgresql.org/support/security/CVE-2026-6464/) caused `psql` to reject these.\n- Several fixes that could cause a dump to fail to restore, or cause a restored\n  view to behave differently from the original. These include views and rules that\n  use `AT TIME ZONE` in a `FROM` clause or a target alias named `set`, `tsvector`\n  and `tsquery` values that could fail to reload.\n- Fix the server becoming stuck, instead of exiting, if the startup process\n  crashes while the server is restarting after a crash.\n\nThis release also updates time zone data files to tzdata release 2026f.\nBeginning in November 2026, Canada's Northwest Territories (America/Inuvik)\nare on year-round UTC-06 and Manitoba (America/Winnipeg) is on year-round\nUTC-05. This release assumes their TZ abbreviations will be CST and EST\nrespectively (though this could change). It also reflects that Cuba will stay\non daylight saving time this winter, and that the `EST5EDT`, `CST6CDT`,\n`MST7MDT`, and `PST8PDT` zone names now use their indicated UTC offsets for\nold timestamps instead of the history of their associated city-named zones.\n\n## Updating\n\nAll PostgreSQL update releases are cumulative. As with other minor releases,\nusers are not required to dump and reload their database or use `pg_upgrade`\nin order to apply this update release; you may simply stop PostgreSQL and\nupdate its binaries.\n\nIf you suspect that a GIN index is affected by one of the corruption issues\nfixed in this release, you should\n[reindex](https://www.postgresql.org/docs/current/sql-reindex.html) it, for\nexample:\n\n`REINDEX INDEX your_index_name;`\n\nIf you use `pg_trgm`, you should reindex any GiST indexes that use the\n`gist_trgm_ops` operator class.\n\nIf you see `missing chunk number` errors when reading a table, you should\nreindex the table, which also reindexes its TOAST table, for example:\n\n`REINDEX TABLE your_table_name;`\n\nIf you use incremental backups, we recommend taking a new full backup after\nupdating and using it as the basis for subsequent incremental backups.\n\nIf you use partitioned tables, the following query finds `NOT NULL NO INHERIT`\nconstraints on partitioned tables:\n\n`SELECT conrelid::regclass, conname\nFROM pg_constraint\nWHERE contype = 'n' AND connoinherit\nAND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');`\n\nYou can remove unwanted constraints with `ALTER TABLE ... DROP CONSTRAINT ...`.\nConstraints you want to keep should be repaired with\n`ALTER TABLE ... ALTER CONSTRAINT ... INHERIT`, which will fail if any of the\ntable's partitions contain `NULL` values in that column.\n\nIf you have B-tree indexes on `bpchar` columns (that is, columns declared as\n`bpchar` without a length), you should reindex them after updating. Columns\ndeclared as `char(n)` are not affected.\n\nUsers who have skipped one or more update releases may need to run additional\npost-update steps; please see the release notes from earlier versions for\ndetails.\n\nFor more details, please see the [release notes](https://www.postgresql.org/docs/release/).\n\n## A Note on PostgreSQL 19 RC 2\n\nThis release marks the second release candidate of PostgreSQL 19. As a release\ncandidate, PostgreSQL 19 RC 2 will be mostly identical to the initial release of\nPostgreSQL 19, though some more fixes may be applied prior to the general\navailability of PostgreSQL 19. PostgreSQL 19 RC 2 also includes the fixes in\nthis update release that apply to PostgreSQL 19.\n\nThe planned date for the general availability of PostgreSQL 19 is\nNovember 19, 2026. Please see the \"Release Schedule\" section for more details.\n\n## Upgrading to PostgreSQL 19 RC 2\n\nTo upgrade to PostgreSQL 19 RC 2 from earlier versions of PostgreSQL, you will\nneed to use a major version upgrade strategy, e.g. `pg_upgrade` or\n`pg_dump` / `pg_restore`. For more information, please visit the documentation\nsection on [upgrading](https://www.postgresql.org/docs/19/upgrading.html):\n\n<https://www.postgresql.org/docs/19/upgrading.html>\n\nIf you use `pg_upgrade` and have indexes that use\n[full text search](https://www.postgresql.org/docs/19/textsearch.html),\n[`pg_trgm`](https://www.postgresql.org/docs/19/pgtrgm.html), or\n[`fuzzystrmatch`](https://www.postgresql.org/docs/19/fuzzystrmatch.html), please\nreview the\n[\"Migration to Version 19\"](https://www.postgresql.org/docs/19/release-19.html#RELEASE-19-MIGRATION)\nsection of the release notes, as you may need to reindex them after upgrading.\n\n## Changes Since 19 RC 1\n\nSeveral bug fixes were applied to PostgreSQL 19 during the RC 1 period. These\ninclude:\n\n- Revert a change that allowed\n  [`JSON_ARRAY()` and `JSON_OBJECT()`](https://www.postgresql.org/docs/19/functions-json.html#FUNCTIONS-JSON-CREATION-TABLE)\n  expressions over arrays, composite types, and range types to be used in\n  expression indexes, generated columns, and partition keys, as these indexes\n  could become out-of-date. If you created any of these objects while testing\n  PostgreSQL 19, you need to drop or redefine them before upgrading, as\n  `pg_dump` / `pg_restore` and `pg_upgrade` will fail to recreate them.\n- Fix wrong results in\n  [`GROUPING SETS`](https://www.postgresql.org/docs/19/queries-table-expressions.html#QUERIES-GROUPING-SETS)\n  queries, where a column not included in the current grouping set could show a\n  value instead of `NULL`.\n- Fix an infinite loop in `first_value()` and `nth_value()` when using\n  [`IGNORE NULLS`](https://www.postgresql.org/docs/19/functions-window.html) with\n  some `EXCLUDE` frame options.\n- Fix [eager aggregation](https://www.postgresql.org/docs/19/runtime-config-query.html#GUC-ENABLE-EAGER-AGGREGATE)\n  running volatile functions in a join condition once per group instead of once\n  per row.\n- Fix [promotion](https://www.postgresql.org/docs/19/warm-standby-failover.html)\n  of a standby server waiting indefinitely if a session is blocked sending data to\n  a client that has stopped reading.\n- Fix the [`LISTEN`](https://www.postgresql.org/docs/19/sql-listen.html) /\n  [`NOTIFY`](https://www.postgresql.org/docs/19/sql-notify.html) queue becoming\n  stuck if a session is interrupted while reading notifications.\n- Fix foreign key checks that could fail with an error when the referencing\n  column's type needs a cast to be compared with the referenced column.\n- Fix performance regressions in hash-based query execution, including hash\n  tables that could be sized far beyond the\n  [`work_mem`](https://www.postgresql.org/docs/19/runtime-config-resource.html#GUC-WORK-MEM)\n  limit based on the planner's row estimate.\n\nFor a detailed list of fixes, please visit the\n[open items](https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items#resolved_before_19rc2)\npage.\n\n## Release Schedule\n\nThis is the second release candidate for PostgreSQL 19. Unless an issue is\ndiscovered that requires a delay or an additional release candidate,\nPostgreSQL 19 should be made generally available on November 19, 2026.\n\nFor further information please see the\n[Beta Testing](https://www.postgresql.org/developer/beta/) page.\n\n## Links\n\n- [Download](https://www.postgresql.org/download/)\n- [Release Notes](https://www.postgresql.org/docs/release/)\n- [Security](https://www.postgresql.org/support/security/)\n- [Versioning Policy](https://www.postgresql.org/support/versioning/)\n- [Beta Testing Information](https://www.postgresql.org/developer/beta/)\n- [PostgreSQL 19 Beta Release Notes](https://www.postgresql.org/docs/19/release-19.html)\n- [PostgreSQL 19 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items)\n- [Submit a Bug](https://www.postgresql.org/account/submitbug/)\n- [Donate](https://www.postgresql.org/about/donate/)\n\nIf you have corrections or suggestions for this release announcement, please send them to the *pgsql-www@lists.postgresql.org* public [mailing list](https://www.postgresql.org/list/).\n","body_html":"<h1 id=\"postgresql-18-7-17-12-16-16-15-20-14-25-and-19-rc-2-released\">PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released!</h1>\n<p>Posted on <strong>2026-11-12</strong> by PostgreSQL Global Development Group</p>\n<p>PostgreSQL Project\n Security</p>\n<p>The PostgreSQL Global Development Group has released an update to all\nsupported versions of PostgreSQL, including 18.7, 17.12, 16.16, 15.20, and\n14.25, as well as the second release candidate of PostgreSQL 19. This release\nfixes 52 security vulnerabilities and over 140 bugs reported over the last\nseveral months.</p>\n<p>There are several issues that may require you to take extra steps after\nupdating, which are described in detail below. See the &quot;Updating&quot; section for\nmore information on post-update steps you may need to take.</p>\n<p>For the full list of changes, please review the <a href=\"https://www.postgresql.org/docs/release/\" rel=\"nofollow ugc noopener\">release\nnotes</a>.</p>\n<h2 id=\"postgresql-14-eol-notice\">PostgreSQL 14 EOL Notice</h2>\n<p><strong>This is the final release of PostgreSQL 14</strong>. PostgreSQL 14 is now end-of-life\nand will no longer receive security and bug fixes. If you are running\nPostgreSQL 14 in a production environment, we suggest that you make plans to\nupgrade to a newer, supported version of PostgreSQL. Please see our\n<a href=\"https://www.postgresql.org/support/versioning/\" rel=\"nofollow ugc noopener\">versioning policy</a> for more\ninformation.</p>\n<h2 id=\"security-issues\">Security Issues</h2>\n<p>The following security vulnerabilities are closed in this update release.\nYou can find more details about the vulnerabilities and their affected versions\nin the links below:</p>\n<ul><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-6460/\" rel=\"nofollow ugc noopener\">CVE-2026-6460</a>: Type confusion after <code>ALTER ... SET DATA TYPE</code> executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-6467/\" rel=\"nofollow ugc noopener\">CVE-2026-6467</a>: Extension script schema mishandling executes arbitrary SQL (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">7.2</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-14661/\" rel=\"nofollow ugc noopener\">CVE-2026-14661</a>: <code>dblink</code> and subscriptions can append to arbitrary files (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\" rel=\"nofollow ugc noopener\">8.1</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-16237/\" rel=\"nofollow ugc noopener\">CVE-2026-16237</a>: <code>INSERT ... ON CONFLICT</code> can read or modify rows despite auto-updatable view <code>WHERE</code> condition (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N\" rel=\"nofollow ugc noopener\">5.4</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-16240/\" rel=\"nofollow ugc noopener\">CVE-2026-16240</a>: <code>pg_basebackup</code> can use backup manifest content as a format string (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">3.7</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-18447/\" rel=\"nofollow ugc noopener\">CVE-2026-18447</a>: Output parameter type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116303/\" rel=\"nofollow ugc noopener\">CVE-2026-116303</a>: Foreign key and JSON conversions bypass <code>EXECUTE</code> privilege on cast functions (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">3.1</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116304/\" rel=\"nofollow ugc noopener\">CVE-2026-116304</a>: Parallel <code>RECORD</code> typmod use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116306/\" rel=\"nofollow ugc noopener\">CVE-2026-116306</a>: Composite-type change during field assignment executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116307/\" rel=\"nofollow ugc noopener\">CVE-2026-116307</a>: <code>plperl</code> prepared-query use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116308/\" rel=\"nofollow ugc noopener\">CVE-2026-116308</a>: <code>dict_int</code> reads beyond zero-length tokens (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116309/\" rel=\"nofollow ugc noopener\">CVE-2026-116309</a>: <code>plperl</code> blessed-reference type confusion may execute arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116310/\" rel=\"nofollow ugc noopener\">CVE-2026-116310</a>: <code>COPY</code> error context uses freed field storage (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116311/\" rel=\"nofollow ugc noopener\">CVE-2026-116311</a>: <code>DROP OWNED</code> can remove restrictive row security policies from non-owned tables (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N\" rel=\"nofollow ugc noopener\">5.4</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116312/\" rel=\"nofollow ugc noopener\">CVE-2026-116312</a>: <code>MERGE</code> can place the wrong row in a trigger transition table (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N\" rel=\"nofollow ugc noopener\">5.4</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116313/\" rel=\"nofollow ugc noopener\">CVE-2026-116313</a>: <code>vacuumdb --missing-stats-only</code> lets a database owner execute code as the <code>vacuumdb</code> user (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">7.2</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116314/\" rel=\"nofollow ugc noopener\">CVE-2026-116314</a>: <code>pg_restore</code> executes arbitrary code due to missing non-plain archive validation (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116315/\" rel=\"nofollow ugc noopener\">CVE-2026-116315</a>: <code>tsvector_delete()</code> heap buffer overflow executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116316/\" rel=\"nofollow ugc noopener\">CVE-2026-116316</a>: Security-restricted operations can create types in pg_temp, which later queries of the session find (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116317/\" rel=\"nofollow ugc noopener\">CVE-2026-116317</a>: <code>ts_rank_cd()</code> heap buffer overflow may execute arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116318/\" rel=\"nofollow ugc noopener\">CVE-2026-116318</a>: <code>pg_dump</code> not-null constraint name allows SQL injection (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116319/\" rel=\"nofollow ugc noopener\">CVE-2026-116319</a>: <code>plperl</code> reentrant <code>return_next()</code> use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116320/\" rel=\"nofollow ugc noopener\">CVE-2026-116320</a>: <code>plperl</code> array and hash conversion use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116321/\" rel=\"nofollow ugc noopener\">CVE-2026-116321</a>: Unterminated name value discloses server memory (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116322/\" rel=\"nofollow ugc noopener\">CVE-2026-116322</a>: Pre-authentication cancel request can leak a spinlock (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\" rel=\"nofollow ugc noopener\">5.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116323/\" rel=\"nofollow ugc noopener\">CVE-2026-116323</a>: <code>pltcl</code> reentrant result conversion use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116325/\" rel=\"nofollow ugc noopener\">CVE-2026-116325</a>: <code>reindexdb</code> index name quoting allows SQL injection (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116326/\" rel=\"nofollow ugc noopener\">CVE-2026-116326</a>: <code>plperl</code> tied-object exceptions follow stale sigjmp_buf (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116327/\" rel=\"nofollow ugc noopener\">CVE-2026-116327</a>: <code>security_barrier</code> analysis can expose hidden values through indirect expressions (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116328/\" rel=\"nofollow ugc noopener\">CVE-2026-116328</a>: Generation memory context integer wraparound executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116329/\" rel=\"nofollow ugc noopener\">CVE-2026-116329</a>: Statistics import type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116330/\" rel=\"nofollow ugc noopener\">CVE-2026-116330</a>: <code>pg_dump</code> tar restore.sql fails to block psql command injection (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116331/\" rel=\"nofollow ugc noopener\">CVE-2026-116331</a>: Min/max aggregate type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116332/\" rel=\"nofollow ugc noopener\">CVE-2026-116332</a>: Portal setup use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116333/\" rel=\"nofollow ugc noopener\">CVE-2026-116333</a>: Parallel B-tree array scan reads beyond array bounds (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\" rel=\"nofollow ugc noopener\">6.5</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116335/\" rel=\"nofollow ugc noopener\">CVE-2026-116335</a>: Commutator or negator result-type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-116336/\" rel=\"nofollow ugc noopener\">CVE-2026-116336</a>: <code>REINDEX CONCURRENTLY</code> does not block <code>DROP INDEX</code> during index functions (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120139/\" rel=\"nofollow ugc noopener\">CVE-2026-120139</a>: Tuple-size integer wraparound executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120141/\" rel=\"nofollow ugc noopener\">CVE-2026-120141</a>: Materialized set-returning function type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120142/\" rel=\"nofollow ugc noopener\">CVE-2026-120142</a>: Dropped-column type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120143/\" rel=\"nofollow ugc noopener\">CVE-2026-120143</a>: Transition-table cursor use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120144/\" rel=\"nofollow ugc noopener\">CVE-2026-120144</a>: Type-cache invalidation gap executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120145/\" rel=\"nofollow ugc noopener\">CVE-2026-120145</a>: Logical replication can write to subscriber system catalogs, executing arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120146/\" rel=\"nofollow ugc noopener\">CVE-2026-120146</a>: <code>REASSIGN OWNED</code> bypasses role <code>SET</code> and <code>CREATEDB</code> checks (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120147/\" rel=\"nofollow ugc noopener\">CVE-2026-120147</a>: <code>dblink</code> reentrant disconnect use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120148/\" rel=\"nofollow ugc noopener\">CVE-2026-120148</a>: Extended-statistics pseudo-type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\" rel=\"nofollow ugc noopener\">8.1</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120149/\" rel=\"nofollow ugc noopener\">CVE-2026-120149</a>: FDW batch-insert mismatch executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120150/\" rel=\"nofollow ugc noopener\">CVE-2026-120150</a>: Expanded-record domain-check use-after-free executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120151/\" rel=\"nofollow ugc noopener\">CVE-2026-120151</a>: <code>plpgsql</code> record-field type confusion executes arbitrary code (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">8.8</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120152/\" rel=\"nofollow ugc noopener\">CVE-2026-120152</a>: <code>pg_show_all_settings()</code> use-after-free discloses memory (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120153/\" rel=\"nofollow ugc noopener\">CVE-2026-120153</a>: Extension-script substitutions allow SQL injection through object names (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H\" rel=\"nofollow ugc noopener\">7.2</a>)</li><li><a href=\"https://www.postgresql.org/support/security/CVE-2026-120154/\" rel=\"nofollow ugc noopener\">CVE-2026-120154</a>: <code>INSERT ... ON CONFLICT</code> can read rows despite row security policies (CVSS v3.1: <a href=\"https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\" rel=\"nofollow ugc noopener\">4.3</a>)</li></ul>\n<h2 id=\"bug-fixes-and-improvements\">Bug Fixes and Improvements</h2>\n<p>This update fixes over 140 bugs that were reported in the last several\nmonths. The issues listed below affect PostgreSQL 18. Many of these issues\nalso affect other supported versions of PostgreSQL.</p>\n<ul><li><p>Fix exporting and importing</p><p><a href=\"https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-SNAPSHOT-SYNCHRONIZATION\" rel=\"nofollow ugc noopener\">snapshots</a>\ntaken on a standby server. The issue was detected when running a parallel\n<a href=\"https://www.postgresql.org/docs/current/app-pgdump.html\" rel=\"nofollow ugc noopener\"><code>pg_dump</code></a> against a\nstandby server, and could corrupt both the dump output and the standby server&#39;s\ndata. More generally, a transaction that imported a snapshot taken on a standby\nserver could return wrong results.</p></li><li><p>Several fixes for <a href=\"https://www.postgresql.org/docs/current/gin.html\" rel=\"nofollow ugc noopener\">GIN</a></p><p>indexes that could lead to index corruption, causing queries to miss rows or to\nreturn unrelated rows. If you suspect a GIN index is affected, you should\nreindex it. See the release notes for more details on the issue, and\nthe &quot;Updating&quot; section for post-update steps.</p></li><li><p>Fix possible index corruption in</p><p><a href=\"https://www.postgresql.org/docs/current/pgtrgm.html\" rel=\"nofollow ugc noopener\"><code>pg_trgm</code></a> GiST indexes\nthat could cause searches to miss matching rows. You need to reindex after\nupdating; see the &quot;Updating&quot; section.</p></li><li><p>Fix a case where, after</p><p><a href=\"https://www.postgresql.org/docs/current/sql-reindex.html\" rel=\"nofollow ugc noopener\"><code>REINDEX CONCURRENTLY</code></a>\nrebuilt an index on a\n<a href=\"https://www.postgresql.org/docs/current/storage-toast.html\" rel=\"nofollow ugc noopener\">TOAST</a> table,\nlater index updates could be missed, leading to <code>missing chunk number</code> errors.\nIf you&#39;ve encountered this issue, after updating, you&#39;ll need to reindex. See\nthe &quot;Updating&quot; section.</p></li><li><p>Disallow <code>NOT NULL NO INHERIT</code> constraints on partitioned tables in all</p><p>cases, including <code>CREATE TABLE ... LIKE</code>. Previously, this could allow a\npartition to contain <code>NULL</code> values when it should not. See the &quot;Updating&quot;\nsection for how to find and repair affected constraints.</p></li><li><p>Disable B-tree index deduplication for columns declared as <code>bpchar</code> without a</p><p>length, which could cause index-only scans to return wrong results. If you have\nB-tree indexes on <code>bpchar</code> columns, you should reindex them after updating. See\nthe &quot;Updating&quot; section.</p></li><li><p>Several fixes for incremental backups that could produce corrupt backups. We</p><p>recommend taking a new full backup after updating and using it for subsequent\nincremental backups. See the &quot;Updating&quot; section.</p></li><li><p>Several fixes for</p><p><a href=\"https://www.postgresql.org/docs/current/app-pgbasebackup.html\" rel=\"nofollow ugc noopener\">base backups</a>,\nincluding avoiding a torn copy of the <code>pg_control</code> file, and avoiding\ntruncated or zero-padded copies of files such as <code>postgresql.auto.conf</code> that\nare replaced while the backup is running.</p></li><li><p>Rework the planner&#39;s join removal implementation. While this is a significant</p><p>change for an update release, it was made to avoid continued bugs from the\nprevious implementation.</p></li><li><p>Fix possible loss of rows during a table rewrite (for example,</p><p><a href=\"https://www.postgresql.org/docs/current/sql-cluster.html\" rel=\"nofollow ugc noopener\"><code>CLUSTER</code></a> or\n<code>VACUUM FULL</code>) when a row had been updated by a subtransaction that later\naborted.</p></li><li>Fix parallel vacuum I/O timing reports.</li><li><p>Several fixes that could cause data loss or inconsistency after a crash,</p><p>including starting a checkpoint while creating a multixact or while aborting a\n<a href=\"https://www.postgresql.org/docs/current/sql-prepare-transaction.html\" rel=\"nofollow ugc noopener\">prepared transaction</a>.\nThis release also writes the state files of pending prepared transactions\natomically, as a crash could previously leave behind an invalid file that\nprevented the server from starting.</p></li><li><p>Several fixes to the planner that could produce wrong query results,</p><p>including queries with <code>LATERAL</code> references, outer joins, self-join elimination\non tables using inheritance, <code>DISTINCT ON</code> in a subquery with set-returning\nfunctions, and queries using non-deterministic collations.</p></li><li><p>Several fixes to [partition</p><p>pruning](<a href=\"https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITION-PRUNING\" rel=\"nofollow ugc noopener\">https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITION-PRUNING</a>)\nthat could cause rows to be missed, including multi-column <code>RANGE</code>-partitioned\ntables when a query filters only on the leading columns, <code>DEFAULT</code> partitions\non tables using <code>MINVALUE</code> or <code>MAXVALUE</code> bounds, and concurrent updates that\ncould silently skip rows that should be updated.</p></li><li><p>Fix [`INSERT ... ON</p><p>CONFLICT<code>](https://www.postgresql.org/docs/current/sql-insert.html#SQL-ON-CONFLICT)\nto acquire a predicate lock on the conflicting row under\n[</code>SERIALIZABLE`](<a href=\"https://www.postgresql.org/docs/current/transaction-iso.html#XACT-SERIALIZABLE\" rel=\"nofollow ugc noopener\">https://www.postgresql.org/docs/current/transaction-iso.html#XACT-SERIALIZABLE</a>)\nisolation. Previously, concurrent updates that should have failed with a\nserialization error could succeed.</p></li><li><p>Fix <a href=\"https://www.postgresql.org/docs/current/sql-merge.html\" rel=\"nofollow ugc noopener\"><code>MERGE</code></a> with</p><p><code>WHEN NOT MATCHED BY SOURCE</code> when the target row is concurrently deleted.\nPreviously, a <code>WHEN NOT MATCHED BY TARGET</code> action could run instead, giving\nincorrect results.</p></li><li><p>Several fixes for</p><p><a href=\"https://www.postgresql.org/docs/current/functions-json.html\" rel=\"nofollow ugc noopener\">SQL/JSON</a>\nfunctions such as <code>JSON_TABLE</code> and <code>JSON_VALUE</code> that could return incorrect\nresults.</p></li><li><p>Several fixes for [logical</p><p>replication](<a href=\"https://www.postgresql.org/docs/current/logical-replication.html\" rel=\"nofollow ugc noopener\">https://www.postgresql.org/docs/current/logical-replication.html</a>)\nthat could cause a subscriber to apply changes incorrectly.</p></li><li><p>Several fixes for [standby</p><p>servers](<a href=\"https://www.postgresql.org/docs/current/hot-standby.html\" rel=\"nofollow ugc noopener\">https://www.postgresql.org/docs/current/hot-standby.html</a>), including\navoiding unnecessary replay delays and query cancellations in certain cases.</p></li><li><p>Fix <a href=\"https://www.postgresql.org/docs/current/app-psql.html\" rel=\"nofollow ugc noopener\"><code>psql</code></a> to accept</p><p>multiple <a href=\"https://www.postgresql.org/docs/current/sql-copy.html\" rel=\"nofollow ugc noopener\"><code>COPY ... FROM STDIN</code></a>\ncommands in a single command string. The fix for <a href=\"https://www.postgresql.org/support/security/CVE-2026-6464/\" rel=\"nofollow ugc noopener\">CVE-2026-6464</a> caused <code>psql</code> to reject these.</p></li><li><p>Several fixes that could cause a dump to fail to restore, or cause a restored</p><p>view to behave differently from the original. These include views and rules that\nuse <code>AT TIME ZONE</code> in a <code>FROM</code> clause or a target alias named <code>set</code>, <code>tsvector</code>\nand <code>tsquery</code> values that could fail to reload.</p></li><li><p>Fix the server becoming stuck, instead of exiting, if the startup process</p><p>crashes while the server is restarting after a crash.</p></li></ul>\n<p>This release also updates time zone data files to tzdata release 2026f.\nBeginning in November 2026, Canada&#39;s Northwest Territories (America/Inuvik)\nare on year-round UTC-06 and Manitoba (America/Winnipeg) is on year-round\nUTC-05. This release assumes their TZ abbreviations will be CST and EST\nrespectively (though this could change). It also reflects that Cuba will stay\non daylight saving time this winter, and that the <code>EST5EDT</code>, <code>CST6CDT</code>,\n<code>MST7MDT</code>, and <code>PST8PDT</code> zone names now use their indicated UTC offsets for\nold timestamps instead of the history of their associated city-named zones.</p>\n<h2 id=\"updating\">Updating</h2>\n<p>All PostgreSQL update releases are cumulative. As with other minor releases,\nusers are not required to dump and reload their database or use <code>pg_upgrade</code>\nin order to apply this update release; you may simply stop PostgreSQL and\nupdate its binaries.</p>\n<p>If you suspect that a GIN index is affected by one of the corruption issues\nfixed in this release, you should\n<a href=\"https://www.postgresql.org/docs/current/sql-reindex.html\" rel=\"nofollow ugc noopener\">reindex</a> it, for\nexample:</p>\n<p><code>REINDEX INDEX your_index_name;</code></p>\n<p>If you use <code>pg_trgm</code>, you should reindex any GiST indexes that use the\n<code>gist_trgm_ops</code> operator class.</p>\n<p>If you see <code>missing chunk number</code> errors when reading a table, you should\nreindex the table, which also reindexes its TOAST table, for example:</p>\n<p><code>REINDEX TABLE your_table_name;</code></p>\n<p>If you use incremental backups, we recommend taking a new full backup after\nupdating and using it as the basis for subsequent incremental backups.</p>\n<p>If you use partitioned tables, the following query finds <code>NOT NULL NO INHERIT</code>\nconstraints on partitioned tables:</p>\n<p><code>SELECT conrelid::regclass, conname\nFROM pg_constraint\nWHERE contype = &#39;n&#39; AND connoinherit\nAND conrelid IN (SELECT oid FROM pg_class WHERE relkind = &#39;p&#39;);</code></p>\n<p>You can remove unwanted constraints with <code>ALTER TABLE ... DROP CONSTRAINT ...</code>.\nConstraints you want to keep should be repaired with\n<code>ALTER TABLE ... ALTER CONSTRAINT ... INHERIT</code>, which will fail if any of the\ntable&#39;s partitions contain <code>NULL</code> values in that column.</p>\n<p>If you have B-tree indexes on <code>bpchar</code> columns (that is, columns declared as\n<code>bpchar</code> without a length), you should reindex them after updating. Columns\ndeclared as <code>char(n)</code> are not affected.</p>\n<p>Users who have skipped one or more update releases may need to run additional\npost-update steps; please see the release notes from earlier versions for\ndetails.</p>\n<p>For more details, please see the <a href=\"https://www.postgresql.org/docs/release/\" rel=\"nofollow ugc noopener\">release notes</a>.</p>\n<h2 id=\"a-note-on-postgresql-19-rc-2\">A Note on PostgreSQL 19 RC 2</h2>\n<p>This release marks the second release candidate of PostgreSQL 19. As a release\ncandidate, PostgreSQL 19 RC 2 will be mostly identical to the initial release of\nPostgreSQL 19, though some more fixes may be applied prior to the general\navailability of PostgreSQL 19. PostgreSQL 19 RC 2 also includes the fixes in\nthis update release that apply to PostgreSQL 19.</p>\n<p>The planned date for the general availability of PostgreSQL 19 is\nNovember 19, 2026. Please see the &quot;Release Schedule&quot; section for more details.</p>\n<h2 id=\"upgrading-to-postgresql-19-rc-2\">Upgrading to PostgreSQL 19 RC 2</h2>\n<p>To upgrade to PostgreSQL 19 RC 2 from earlier versions of PostgreSQL, you will\nneed to use a major version upgrade strategy, e.g. <code>pg_upgrade</code> or\n<code>pg_dump</code> / <code>pg_restore</code>. For more information, please visit the documentation\nsection on <a href=\"https://www.postgresql.org/docs/19/upgrading.html\" rel=\"nofollow ugc noopener\">upgrading</a>:</p>\n<p><a href=\"https://www.postgresql.org/docs/19/upgrading.html\" rel=\"nofollow ugc noopener\">https://www.postgresql.org/docs/19/upgrading.html</a></p>\n<p>If you use <code>pg_upgrade</code> and have indexes that use\n<a href=\"https://www.postgresql.org/docs/19/textsearch.html\" rel=\"nofollow ugc noopener\">full text search</a>,\n<a href=\"https://www.postgresql.org/docs/19/pgtrgm.html\" rel=\"nofollow ugc noopener\"><code>pg_trgm</code></a>, or\n<a href=\"https://www.postgresql.org/docs/19/fuzzystrmatch.html\" rel=\"nofollow ugc noopener\"><code>fuzzystrmatch</code></a>, please\nreview the\n<a href=\"https://www.postgresql.org/docs/19/release-19.html#RELEASE-19-MIGRATION\" rel=\"nofollow ugc noopener\">&quot;Migration to Version 19&quot;</a>\nsection of the release notes, as you may need to reindex them after upgrading.</p>\n<h2 id=\"changes-since-19-rc-1\">Changes Since 19 RC 1</h2>\n<p>Several bug fixes were applied to PostgreSQL 19 during the RC 1 period. These\ninclude:</p>\n<ul><li><p>Revert a change that allowed</p><p><a href=\"https://www.postgresql.org/docs/19/functions-json.html#FUNCTIONS-JSON-CREATION-TABLE\" rel=\"nofollow ugc noopener\"><code>JSON_ARRAY()</code> and <code>JSON_OBJECT()</code></a>\nexpressions over arrays, composite types, and range types to be used in\nexpression indexes, generated columns, and partition keys, as these indexes\ncould become out-of-date. If you created any of these objects while testing\nPostgreSQL 19, you need to drop or redefine them before upgrading, as\n<code>pg_dump</code> / <code>pg_restore</code> and <code>pg_upgrade</code> will fail to recreate them.</p></li><li><p>Fix wrong results in</p><p><a href=\"https://www.postgresql.org/docs/19/queries-table-expressions.html#QUERIES-GROUPING-SETS\" rel=\"nofollow ugc noopener\"><code>GROUPING SETS</code></a>\nqueries, where a column not included in the current grouping set could show a\nvalue instead of <code>NULL</code>.</p></li><li><p>Fix an infinite loop in <code>first_value()</code> and <code>nth_value()</code> when using</p><p><a href=\"https://www.postgresql.org/docs/19/functions-window.html\" rel=\"nofollow ugc noopener\"><code>IGNORE NULLS</code></a> with\nsome <code>EXCLUDE</code> frame options.</p></li><li><p>Fix <a href=\"https://www.postgresql.org/docs/19/runtime-config-query.html#GUC-ENABLE-EAGER-AGGREGATE\" rel=\"nofollow ugc noopener\">eager aggregation</a></p><p>running volatile functions in a join condition once per group instead of once\nper row.</p></li><li><p>Fix <a href=\"https://www.postgresql.org/docs/19/warm-standby-failover.html\" rel=\"nofollow ugc noopener\">promotion</a></p><p>of a standby server waiting indefinitely if a session is blocked sending data to\na client that has stopped reading.</p></li><li><p>Fix the <a href=\"https://www.postgresql.org/docs/19/sql-listen.html\" rel=\"nofollow ugc noopener\"><code>LISTEN</code></a> /</p><p><a href=\"https://www.postgresql.org/docs/19/sql-notify.html\" rel=\"nofollow ugc noopener\"><code>NOTIFY</code></a> queue becoming\nstuck if a session is interrupted while reading notifications.</p></li><li><p>Fix foreign key checks that could fail with an error when the referencing</p><p>column&#39;s type needs a cast to be compared with the referenced column.</p></li><li><p>Fix performance regressions in hash-based query execution, including hash</p><p>tables that could be sized far beyond the\n<a href=\"https://www.postgresql.org/docs/19/runtime-config-resource.html#GUC-WORK-MEM\" rel=\"nofollow ugc noopener\"><code>work_mem</code></a>\nlimit based on the planner&#39;s row estimate.</p></li></ul>\n<p>For a detailed list of fixes, please visit the\n<a href=\"https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items#resolved_before_19rc2\" rel=\"nofollow ugc noopener\">open items</a>\npage.</p>\n<h2 id=\"release-schedule\">Release Schedule</h2>\n<p>This is the second release candidate for PostgreSQL 19. Unless an issue is\ndiscovered that requires a delay or an additional release candidate,\nPostgreSQL 19 should be made generally available on November 19, 2026.</p>\n<p>For further information please see the\n<a href=\"https://www.postgresql.org/developer/beta/\" rel=\"nofollow ugc noopener\">Beta Testing</a> page.</p>\n<h2 id=\"links\">Links</h2>\n<ul><li><a href=\"https://www.postgresql.org/download/\" rel=\"nofollow ugc noopener\">Download</a></li><li><a href=\"https://www.postgresql.org/docs/release/\" rel=\"nofollow ugc noopener\">Release Notes</a></li><li><a href=\"https://www.postgresql.org/support/security/\" rel=\"nofollow ugc noopener\">Security</a></li><li><a href=\"https://www.postgresql.org/support/versioning/\" rel=\"nofollow ugc noopener\">Versioning Policy</a></li><li><a href=\"https://www.postgresql.org/developer/beta/\" rel=\"nofollow ugc noopener\">Beta Testing Information</a></li><li><a href=\"https://www.postgresql.org/docs/19/release-19.html\" rel=\"nofollow ugc noopener\">PostgreSQL 19 Beta Release Notes</a></li><li><a href=\"https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items\" rel=\"nofollow ugc noopener\">PostgreSQL 19 Open Issues</a></li><li><a href=\"https://www.postgresql.org/account/submitbug/\" rel=\"nofollow ugc noopener\">Submit a Bug</a></li><li><a href=\"https://www.postgresql.org/about/donate/\" rel=\"nofollow ugc noopener\">Donate</a></li></ul>\n<p>If you have corrections or suggestions for this release announcement, please send them to the <em>pgsql-www@lists.postgresql.org</em> public <a href=\"https://www.postgresql.org/list/\" rel=\"nofollow ugc noopener\">mailing list</a>.</p>","headings":[{"level":1,"text":"PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released!","id":"postgresql-18-7-17-12-16-16-15-20-14-25-and-19-rc-2-released"},{"level":2,"text":"PostgreSQL 14 EOL Notice","id":"postgresql-14-eol-notice"},{"level":2,"text":"Security Issues","id":"security-issues"},{"level":2,"text":"Bug Fixes and Improvements","id":"bug-fixes-and-improvements"},{"level":2,"text":"Updating","id":"updating"},{"level":2,"text":"A Note on PostgreSQL 19 RC 2","id":"a-note-on-postgresql-19-rc-2"},{"level":2,"text":"Upgrading to PostgreSQL 19 RC 2","id":"upgrading-to-postgresql-19-rc-2"},{"level":2,"text":"Changes Since 19 RC 1","id":"changes-since-19-rc-1"},{"level":2,"text":"Release Schedule","id":"release-schedule"},{"level":2,"text":"Links","id":"links"}]}}