PostgreSQL 19 Slips to November After AI Review Found 40 Bugs
PostgreSQL 19 general availability slipped to late November after AI-assisted code review surfaced roughly 40 defect reports, forcing 8 to 10 feature reverts late in the cycle. Percona's Zsolt Parragi apologized for his part, noted security fixes jumped from single digits to 44 this year, and said current AI models now find as many issues as human reviewers.
On this page
The delay and the apology
PostgreSQL 19 was expected to reach general availability in September, but after repeated slips the release is now slated for late November. Percona developer Zsolt Parragi published an apology on 15 October titled "Apologies for delaying Postgres 19," half-jokingly taking responsibility as the contributor behind a last-minute revert of a major feature, and calling out committers Robert Haas, Noah Misch, and Andres Freund, whose reverts stabilized the release, while stressing they should not be harassed for it.
The delay's cause was a long tail of late defect reports: roughly 40 issues surfaced near the end of the cycle, forcing 8 to 10 feature reverts, including SQL/PGQ support. LWN's coverage in September noted the warning that shipping on the original schedule could have left unfixable post-release bugs in the wild until version 20.
Where the AI reviews came in
The report's thread on AI tools is unusually concrete. New models, Parragi writes, significantly improved issue detection through the cycle, but every major model upgrade, starting with Fable 5 in June and running through Opus 5.5 and GPT-6 in September, landed after PG19's feature freeze, so the payoff arrives with PG20. Current models now find as many issues as human reviewers, though they still need guidance to filter noise and lack design-level judgment.
Percona's response: daily AI review automation now runs on committed code. Parragi's lesson for the community: pay attention to already-committed code, because the reviews that would have caught PG19's late defects were checking work that was already merged.
Security fixes, and what ships in PG20
The report also quantifies what the community calls the vulnpocalypse: security fixes per year jumped from a typical 2 to 8 in 2020 through 2025, to 44 so far in 2026, including 28 in August alone, with ten committers handling that month versus the usual one or two. Parragi expects November's release to exceed that count.
For PG20: the reverted features may return, new features will ship, and the scope is unpredictable, Parragi writes, closing with "Stay tuned for my next apology! The community is also discussing shortening the minor release cadence and easing the committer path." Community discussions include shortening the minor release cadence and easing the committer path, and he promotes hackorum.dev, which offers auto-built Docker images for testing patches. For teams running PostgreSQL in production, the practical takeaway is to plan for a November 19 upgrade window and to watch the security-fix cadence, which is the real signal in this story. The willingness to delay a major release rather than ship known defects is itself worth reading alongside the AI-review lesson: tools that find bugs are useful only if the team acts on what they find before the deadline.
For teams running PostgreSQL in production, the practical lesson is to budget time for the reviews that AI tooling generates, not just the code they check. The project's own data shows that security fixes and late-cycle reverts are now the norm, and the difference between a clean release and a delayed one is whether the team has time to act on what the tools surface before the deadline arrives.