Log in Sign up
Opinion He Sold Everything and Rode a Bus 2,000 km to Marry an AI Farm Girl With 300,000 Followers Business Anthropic Pledges 5 Percent of Itself to a Public Interest Fund That Grows With Its Valuation AI Agents NVIDIA Open-Sources ASPIRE, the Robot Framework That Turns Failed Grasps Into a Growing Skill Library Coding Assistants PostgreSQL 19 Slips to November 19 After LLM-Assisted Code Review Turned Up Forty Defect Reports News VAST Open-Sources EdenLive, a 5B Real-Time World Model That Tops 24 FPS at 720p on a Single RTX 5090 Business Nvidia Tells Samsung, SK Hynix and Micron to Build Its Custom HBM Base Dies on TSMC's 3nm Process Claude At Anthropic, Junior Share of Technical Staff Fell From 21 Percent to 14 Percent in a Year News Holyvolt Raises 45 Million Dollars at a 245 Million Valuation to Let AI Pick the Next Battery Chemistry Opinion He Sold Everything and Rode a Bus 2,000 km to Marry an AI Farm Girl With 300,000 Followers Business Anthropic Pledges 5 Percent of Itself to a Public Interest Fund That Grows With Its Valuation AI Agents NVIDIA Open-Sources ASPIRE, the Robot Framework That Turns Failed Grasps Into a Growing Skill Library Coding Assistants PostgreSQL 19 Slips to November 19 After LLM-Assisted Code Review Turned Up Forty Defect Reports News VAST Open-Sources EdenLive, a 5B Real-Time World Model That Tops 24 FPS at 720p on a Single RTX 5090 Business Nvidia Tells Samsung, SK Hynix and Micron to Build Its Custom HBM Base Dies on TSMC's 3nm Process Claude At Anthropic, Junior Share of Technical Staff Fell From 21 Percent to 14 Percent in a Year News Holyvolt Raises 45 Million Dollars at a 245 Million Valuation to Let AI Pick the Next Battery Chemistry

PostgreSQL 19 Slips to November 19 After LLM-Assisted Code Review Turned Up Forty Defect Reports

Coding Assistants · By: AIReport Admin · 2 hours ago · 👁 7
PostgreSQL 19 Slips to November 19 After LLM-Assisted Code Review Turned Up Forty Defect Reports

PostgreSQL 19 has moved from late September to around November 19 after LLM-assisted code review surfaced roughly forty defect reports late in the beta window. Eight to ten features, including SQL Property Graph Queries, were reverted to PostgreSQL 20. Committer Peter Eisentraut says the quality bar rose after the code was already written.

The next major release of the world's most widely used open-source database will be late, and the reason is unusual: the reviewers got better. PostgreSQL 19, originally expected in late September or early October, is now targeted for general availability on November 19, with a second release candidate planned for November 12. Between eight and ten significant features have been pulled from the release and postponed to PostgreSQL 20.

The proximate cause, according to Peter Eisentraut, a veteran PostgreSQL committer and vice president at EDB, is a wave of defect reports generated by LLM-assisted code review. In a blog post published October 9, titled "The reverts will continue until morale improves," Eisentraut explained that the tooling surfaced a long tail of "relatively harmless issues involving various edge cases" that in previous cycles would have trickled out over roughly five years of post-release patching. Compressed into a single beta window, that backlog became a queue of roughly forty reports — each carrying fixed overhead for triage, reproduction, patch, review and testing, even when the fix itself was three lines long.

The most prominent casualty is SQL Property Graph Queries (SQL/PGQ), part of the SQL standard since 2023, which lets developers query graph-shaped data inside an ordinary relational database. Its revert touched 47 commits. It is joined by online data checksums (30 commits, partially reverted), UPDATE and DELETE with FOR PORTION OF (23), ALTER TABLE with MERGE/SPLIT PARTITION (14) and the pg_get_*_ddl() functions (13). Long-time contributor Tom Lane had warned in September that he would "be willing to bet dinner" that shipping SQL/PGQ in v19 would produce bugs that could not be fixed until v20.

Eisentraut was explicit that this is not a story about sloppy AI-generated code. The features were written the old way, before "vibe coding" was even available. What changed was the scrutiny: "The effective quality bar has been raised after the time the feature was written and committed." Code that cleared an older standard was suddenly re-judged against a newer one, inside a release window that did not move. He also noted that senior developers spent April through August on security fixes — the August minor release of PostgreSQL 18 shipped 28 CVE fixes against a typical one or two — thinning the human review capacity the beta would normally have had.

Community data supports the AI-driven shift. An analysis of the 937 commits made after beta 1 found 23 that explicitly credit AI assistance, an AI tool or an AI lab — a floor, since only explicit mentions count. A Snowflake engineering post from September 16 describes contributors using AI tools to hunt bugs and build reproducible test cases, including one who ran a "scary bug contest" with AI help. PostgreSQL has no formal AI contribution policy yet; one is expected soon.

Not everything was cut. REPACK CONCURRENTLY, which reclaims disk space without the table lock that VACUUM FULL requires, stays in version 19, as does the bulk of the release. Developers who built migrations or runbooks against beta-era code should run compatibility checks before the November date. The postponed work heads to PostgreSQL 20, which had been expected to carry no new features at all.

The episode is a clean demonstration of an arithmetic problem now facing every software project: when review finds defects faster than a fixed release window can close them, features leave the release. Detection scaled; remediation did not. Eisentraut expects the imbalance to sort itself out in future cycles unless LLM-assisted review keeps improving at its current rate — which, if the past year is any guide, is exactly what it will do.

Comments (0)

Log in to join the discussion

Log In

No comments yet