PostgreSQL 19 delayed by a flood of AI-generated bug reports and patches

Phoronix reports that PostgreSQL 19 will be late. The database server usually ships its annual feature release between September and October, but this year it will not arrive before November, and it could take longer. The article is by Michael Larabel and dated October 30, 2026.

According to the article, the cause is the extra workload developers face from a rise in bug reports and patches generated by AI and large language model (LLM) activity. The team, Phoronix says, is overwhelmed. On top of the bug reports produced by AI agents, it also has to handle backports of security and bug fixes to older PostgreSQL versions.

The article draws on a blog post by PostgreSQL developer Robert Haas, who explains the delay and attributes it to AI. Haas says this would also explain the high number of late reverts and the delay of the release itself. He identifies two factors.

The first is that far more bugs are now being found, and fixing them takes longer. According to Haas, LLMs can draft fixes, but they are not always correct or up to PostgreSQL's standards. That is why humans still review and commit them, and, in his words, those humans have not become any smarter between 2025 and 2026.

The second factor is that some of the time that would have gone into reviewing what was going into the release was diverted to dealing with security issues and other bugs in the back-branches. That delayed the work of determining which changes needed to be reverted before v19 shipped.

The upshot is that AI speeds up bug discovery faster than humans can review and validate the fixes. The bottleneck is not finding bugs or drafting patches but human review, and that is affecting the release schedule.

The article links to other Phoronix stories on the same phenomenon, including one that describes the use of AI and LLMs as a kind of “denial-of-service attack” on open-source maintainers. We were only able to read the Phoronix piece, not Haas's original post, so we cannot add further details or figures about the delay.