PostgreSQL 19 Running Behind Schedule Due to AI/LLM Burden

PostgreSQL 19, the database system’s next annual feature release, is running late. Releases normally arrive around September or October, but version 19 is now expected no earlier than November and could take longer. Developer Robert Haas attributes the delay in large part to a sharp rise in bug reports and proposed fixes generated or submitted with the help of AI and large language models. The extra reports have increased the number of defects developers must investigate, while AI-generated patches still require human review: they can be incorrect or fail to meet PostgreSQL’s coding and project standards.

The added workload has also affected decisions about what can safely ship. Developers spent time addressing security problems and other bugs in older, maintained PostgreSQL branches, diverting attention from reviewing version 19. With less capacity available for release review, it took longer to identify changes that needed to be reverted; Haas connects this pressure to a number of late reverts as well as the delayed release. The central issue is not simply that AI tools produce more candidate fixes, but that their output does not remove the need for experienced developers to assess, repair, and approve the work. Meanwhile, the same people must maintain existing versions and prepare the new release, creating a growing burden on the project’s limited human review capacity.