InfrastructureCompute, chips & cloud
PostgreSQL 19 ships two months late after AI code review surfaces a backlog of old bugs
PostgreSQL 19 arrived on 19 November 2026, about two months late, after LLM-driven code review surfaced latent bugs faster than maintainers could fix them. Graph queries and other features were cut, while replica read-your-writes consistency and non-blocking REPACK shipped.
From the Simon Willison article of November 19, 2026 and cited sources: The project missed its usual September window and pulled SQL/PGQ graph queries, temporal FOR PORTION OF updates, partition merge/split and online checksum toggling in Beta 4. [2] [5] [6]
SOURCES[2] The Register: Postgres 19 delayed after AI reviewers find… theregister.com[5] PostgreSQL 19 Beta 4 Released postgresql.org[6] Neon: Postgres 19 is late, and it's AI's fault neon.com
AI-assisted, not human-edited. Methodology Corrections Who owns this site
- What happened
- The project missed its usual September window and pulled SQL/PGQ graph queries, temporal FOR PORTION OF updates, partition merge/split and online checksum toggling in Beta 4. [2] [5] [6]
- Original source
- Simon Willison article, independent perspective
- Brief by
- AT Pulse research desk AI-assisted; publisher and contact on the desk page
- When
- November 19, 2026 article published
- Covered
- Nov 20 edition
- Evidence
- 9 sources across 6 sites
- 1PostgreSQL 19 Releasedsimonwillison.net
- 2The Register: Postgres 19 delayed after AI reviewers find…theregister.com
- 3PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2…postgresql.org
- 4PostgreSQL: PostgreSQL 19 Released!postgresql.org
- 5PostgreSQL 19 Beta 4 Releasedpostgresql.org
- 6Neon: Postgres 19 is late, and it's AI's faultneon.com
Reach: not measured yet
The project missed its usual September window and pulled SQL/PGQ graph queries, temporal FOR PORTION OF updates, partition merge/split and online checksum toggling in Beta 4. Committers say AI reviewers raised the quality bar after these features were committed. Most fixes were small, but there were a great many of them. The cut features are now aimed at PostgreSQL 20. [2] [5] [6]
The security load jumped. One November minor release fixed 52 CVEs and more than 140 bugs across versions 14 to 18, and 22 of those CVEs credit Anthropic or OpenAI security programs. Disclosed CVEs reached 96 in 2026, up from 7 in 2025. Back-branch commits rose about 60% year on year. The most severe flaw traces back to 2004. [3] [6] [8] [9]
Version 19 adds WAIT FOR LSN, so an application can read its own writes from a replica after a timed wait instead of maintaining custom stick-to-primary logic. It also adds REPACK (CONCURRENTLY) as a non-blocking replacement for VACUUM FULL and CLUSTER, and extensions that pin query plans without code changes. JIT is now off by default and TOAST compression defaults to lz4. [1] [4] [7]
committers report much higher fix volumes, and 22 of the 52 November CVEs credit AI security programs.
Read the full assessment
Implication: AI auditing can become a release-schedule risk for open-source projects, while PostgreSQL users face urgent patching and can drop custom replica workarounds.
Executive brief
PostgreSQL 19 shipped on 19 November 2026, about two months after the usual September window. The delay came largely from LLM-driven code review. AI tools found old bugs faster than maintainers could fix them, and the project dropped SQL/PGQ graph queries and several other features to ship (The Register). The week before, a single minor release fixed a record 52 CVEs (PostgreSQL). Version 19 itself adds read-your-writes consistency on replicas (WAIT FOR LSN), non-blocking REPACK and plan-pinning extensions (PostgreSQL 19 announcement).
What changed and event timeline
Beta 4 drops features
SQL/PGQ, online checksum toggling,
FOR PORTION OFtemporal DML, MERGE/SPLIT PARTITIONS and the DDL-retrieval functions were reverted. At that point general availability was still planned for October ().Delay blamed on AI reviewers
Committer Peter Eisentraut said LLM review had raised the quality bar after these features were committed. Each fix averaged about three lines, but there were many of them ().
Committer quantifies the surge
Robert Haas reported that back-branch commits rose 60% year on year (724 to 1,169) and master commits went from 1,037 to 1,443 ().
Record security release and RC 2
The 18.7/17.12/16.16/15.20/14.25 releases fixed 52 CVEs and more than 140 bugs. Version 14 reached end of life ().
PostgreSQL 19 GA
The release covers workload management, replication, performance and security (). Simon Willison picked out
WAIT FOR LSNas its standout feature ().
Capabilities and access
PostgreSQL 19.0 is open source. Upgrades go through pg_dumpall/restore, pg_upgrade or logical replication (release notes).
Read the full section
PostgreSQL 19.0 is open source. Upgrades go through pg_dumpall/restore, pg_upgrade or logical replication (release notes). Headline features, all from the announcement:
WAIT FOR LSNfor read-your-writes consistency on standbys.REPACK (CONCURRENTLY), which replacesVACUUM FULLandCLUSTER.pg_plan_adviceandpg_stash_advicefor pinning query plans.- Sequence replication via
FOR ALL SEQUENCES. - TLS SNI through
pg_hosts.conf. - Parallel index autovacuum.
INSERT … ON CONFLICT DO SELECTand JSON output fromCOPY.
Technical analysis for researchers and developers
- Read-your-writes on replicas. After a write, the app records
pg_current_wal_insert_lsn(). The release notes also list a no-throw option (release notes). pg_stash_adviceapplies stored advice by query identifier, so a slow plan can be fixed without changing application code (announcement).- JIT is now off by default because its cost estimates proved unreliable. TOAST compression now defaults to lz4 (announcement).
Read the full section
- Read-your-writes on replicas. After a write, the app records
pg_current_wal_insert_lsn(). On the next request it runsWAIT FOR LSN '<lsn>' WITH (TIMEOUT …)on the replica before reading. If the replica hasn't caught up within the timeout, the command raises an error (Simon Willison). This replaces hand-rolled versions of the pattern, such as MediaWiki's code built on MySQL GTIDs. The release notes also list a no-throw option (release notes). - Plan stability.
pg_stash_adviceapplies stored advice by query identifier, so a slow plan can be fixed without changing application code (announcement). - Changed defaults. JIT is now off by default because its cost estimates proved unreliable. TOAST compression now defaults to lz4 (announcement).
Claims and evidence
- The roughly 2x speed-up on foreign-key bulk inserts is the project's own measurement (announcement). No independent benchmark of it has been published.
- 22 of the 52 November CVEs credit AI programs: Anthropic's OSS program and Claude (alongside Ada Logics), OpenAI Codex Security and OpenAI's Security Research Team (HeroDevs).
- PostgreSQL disclosed 96 CVEs in 2026, against 7 in all of 2025 (HeroDevs).
Read the full section
- The roughly 2x speed-up on foreign-key bulk inserts is the project's own measurement (announcement). No independent benchmark of it has been published.
- 22 of the 52 November CVEs credit AI programs: Anthropic's OSS program and Claude (alongside Ada Logics), OpenAI Codex Security and OpenAI's Security Research Team (HeroDevs).
- PostgreSQL disclosed 96 CVEs in 2026, against 7 in all of 2025 (HeroDevs).
- The causal link to AI comes from committers' own accounts (Neon, The Register). The Beta 4 notice itself gives reliability and a predictable schedule as the reasons for the reverts (Beta 4).
Context and prior work
- CVE counts per PostgreSQL 18 minor release rose from 2 to 5, 11, 28 and then 52 (Vonng blog).
- Haas describes the backlog as decades of latent bugs that LLMs are good at finding (Neon).
- The most severe flaw, CVE-2026-6460, is a type-confusion RCE whose root cause dates to 2004 (HeroDevs).
Read the full section
- CVE counts per PostgreSQL 18 minor release rose from 2 to 5, 11, 28 and then 52 (Vonng blog).
- Haas describes the backlog as decades of latent bugs that LLMs are good at finding (Neon).
- The most severe flaw, CVE-2026-6460, is a type-confusion RCE whose root cause dates to 2004 (HeroDevs).
- Willison traces the read-your-writes pattern to MediaWiki, which already did this by hand on MySQL replication (Simon Willison).
Limitations, safety and contested findings
standard_conforming_stringsis now forced on, RADIUS and MULE_INTERNAL encoding are removed, MD5 password logins trigger warnings, and some btree_gist inet indexes need rebuilding (release notes).- The November minors require reindexing GIN indexes and some bpchar B-tree indexes (PostgreSQL).
- Contested reading of the CVE spike.
Read the full section
- Breaking changes.
standard_conforming_stringsis now forced on, RADIUS and MULE_INTERNAL encoding are removed, MD5 password logins trigger warnings, and some btree_gist inet indexes need rebuilding (release notes). - Post-patch steps. The November minors require reindexing GIN indexes and some bpchar B-tree indexes (PostgreSQL).
- Contested reading of the CVE spike. Ruohang Feng (Vonng) argues the high count is a healthy sign that the project is actively maintained, not evidence of decay (Vonng blog).
Business and practitioner implications
- Teams on versions 14–18 should apply the November minors. Version 14 gets no further updates (PostgreSQL).
- Read-scaled apps can drop custom "stick to primary after write" logic in favour of
WAIT FOR LSN. - Re-enable JIT only where you've benchmarked a benefit.
Read the full section
- Patch now. Teams on versions 14–18 should apply the November minors. Version 14 gets no further updates (PostgreSQL).
- Replica routing. Read-scaled apps can drop custom "stick to primary after write" logic in favour of
WAIT FOR LSN. - Analytics workloads. Re-enable JIT only where you've benchmarked a benefit.
- Planning for AI-era security load. For open-source maintainers and vendors, PostgreSQL 19 shows AI auditing turning into release-schedule risk: expect more patches and more cut features. Reverted features such as SQL/PGQ are now aimed at PostgreSQL 20 (The Register).
The source trail.
Sources (9)
PostgreSQL 19 Released
Article text retrieved; extracted text may omit tables or interactive elements.
simonwillison.net