Postgres 19 delayed after AI reviewers find more bugs than humans can fix
PostgreSQL’s latest major release is now expected around November 19 after developers reverted between eight and 10 features during beta review.
TL;DR
- PostgreSQL 19 is now expected around November 19, later than its previously anticipated late-September or early-October release.
- The Register and original committer Peter Eisentraut say AI-assisted review surfaced a large backlog of defects, while some features also had deeper architectural problems.
- The reports describe a timing and feature-scope change; they do not establish that AI review alone caused the delay.
The PostgreSQL Global Development Group delayed PostgreSQL 19, which is now expected to become generally available around November 19, The Register reported. Developers also removed between eight and 10 significant features, which are expected to move to PostgreSQL 20. [1] [3]
Peter Eisentraut, a leading PostgreSQL committer, wrote that some reverted features had architectural defects, while AI-assisted review surfaced many smaller edge-case reports late in beta. He said the additional fixes created a workload that could not be completed within the existing schedule. [1] [3]
Eisentraut also cited reduced review and testing during a period when senior developers were focused on security fixes. He said the affected code largely predated current LLM-assisted review capabilities and rejected “vibe coding” as the explanation for the reverts. [1] [3]
The reporting therefore describes several contributing factors rather than a single cause: feature complexity, security work, late discovery and increased review capacity. The project’s revised release timing and final feature set remain subject to development progress. Hacker News discussion of The Register report reflected debate about whether AI review can improve quality while adding work for maintainers. [1] [2] [3]
Why it matters
The episode illustrates a software-development trade-off: stronger review can reveal defects earlier, but fixing a large backlog can delay a release. The project’s account points to multiple causes and does not isolate AI review as the sole driver.
Editor's note
Distinguishes the project committer’s explanation from The Register’s report; attributes the schedule and feature estimates to the sources.