PostgreSQL 19

PostgreSQL 19's release is running late, with developer Robert Haas attributing the delay to an unusually high number of bugs being found in the codebase. In a blog post he connects the bug surge to AI-assisted development generating more testing and code scrutiny. The PostgreSQL community is debating whether this reflects healthier testing or AI-produced low-quality contributions straining maintainers.

The next major release of the PostgreSQL database is reportedly running late, with maintainers attributing delays to the volume of AI- and LLM-generated contributions that require extra review and cleanup. Developers say vetting low-quality or machine-written patches is consuming time normally spent on the release itself.

A new blog post by longtime PostgreSQL contributor Robert Haas argues that the release of Postgres 19 has fallen behind schedule, attributing the delay to the surge of AI-generated patches and automated contributions flooding the development process. The claim has sparked debate among developers about how AI tooling is affecting open-source review workloads and release timelines.

The release of PostgreSQL 19, the widely used open-source database, has been delayed to 19 November 2026. In a blog post published on 30 October, developer Robert Haas attributed the delay to the influx of bugs reported with the help of AI tools, and questioned how the project should handle this new volume of automated bug submissions.

Michael Stonebraker, who created Postgres, and longtime project contributor Bruce Momjian argue that enterprise AI needs a database no single company controls. In a partner feature, they point to PostgreSQL 19 as a sign of where the open-source database is heading, framing community-governed infrastructure as the right foundation for AI workloads.

The PostgreSQL 19 database release is running behind schedule. The project typically ships its annual feature release each September or October, but this year's version is expected no earlier than November, and possibly later. Developers cite an increased burden from AI and LLM-related work as a factor slowing progress, a development drawing attention in the open-source database community.