PostgreSQL 19 slips to November after LLM-assisted review turns up more defects than the project could fix

Eisentraut, a PostgreSQL committer who works at EDB, writes that about 8 to 10 significant features were reverted from the PostgreSQL 19 branch after beta began, against roughly one per cycle as normal. He attributes part of it to LLM-assisted code review: issues that "would not have surfaced until much later" now surface at once, "and then you're staring at a list of like forty defect reports." Even at three lines each, he says, a fixed overhead per report means "you run out of time." He adds that most affected features were written before such review was useful, so the effective quality bar rose after they were committed. He also lists other factors: some features had real architectural defects, and senior developers were pulled onto security fixes during part of the cycle. He describes it as "just my opinions at this point." The Register reports the release is now expected around November 19.

He does not blame "vibe coding," since the code predates it, and he argues that LLM-assisted fuzzing should become part of feature development.

Why it matters: This is a maintainer's account, not a measurement, and it mixes several causes. It is still a concrete case of review capacity outrunning fix capacity: if your reviewer is cheap and your fixers are not, the backlog shows up at release time. Item 1 shows one response on the review side, a round cap; it does not address the fix-capacity side.