<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t" -->

---
title: Postgres 19 is late, and it's AI's fault | daily.dev
description: PostgreSQL 19 is delayed until November because LLMs are finding bugs faster than committers can fix them, Robert Haas writes. Three major features,...
canonical: https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Postgres 19 is late, and it's AI's fault | daily.dev
og:description: PostgreSQL 19 is delayed until November because LLMs are finding bugs faster than committers can fix them, Robert Haas writes. Three major features,...
og:url: https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t
og:image: https://api.daily.dev/og/posts/4maW4Xj9t.png
og:image:alt: Postgres 19 is late, and it's AI's fault
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Postgres 19 is late, and it's AI's fault

**[Neon](https://daily.dev/sources/neontech)** · 5 min read · 0 upvotes · 0 comments

## Summary

PostgreSQL 19 is delayed until November because LLMs are finding bugs faster than committers can fix them, Robert Haas writes. Three major features, UPDATE/DELETE FOR PORTION OF, SQL/PGQ, and ALTER TABLE MERGE/SPLIT PARTITION, were reverted between August 27 and September 15. Back-patched commits to REL_19_STABLE jumped more than 60% compared to the prior year's cycle, and back-patches to the previous stable release jumped over 74%. LLM-drafted fixes still need human review, which slowed the release process. Haas calls the delay not concerning, since it reflects the project's focus on quality.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://neon.com/blog/postgres-19-is-late-and-its-ais-fault>

## Questions this post answers

### why is PostgreSQL 19 release delayed

PostgreSQL 19 is delayed past its usual September-October window and most likely won't ship until November because LLMs are finding bugs in the codebase faster than committers can fix and review them. Back-patched commits jumped more than 60% year over year, diverting reviewer time and forcing three major features to be reverted late in the beta period.

_Tracking a major database release slip? Follow PostgreSQL 19 developments as they land on daily.dev._

### which features were reverted from PostgreSQL 19 beta

Three major features were pulled from PostgreSQL 19 between August 27 and September 15: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE MERGE PARTITION/SPLIT PARTITION. All three were reverted late in the beta cycle, which is unusual compared to prior years' feature-freeze-adjacent reverts.

_Developers planning around these partition and graph query features can watch for updates on daily.dev._

### how many bugs are LLMs finding in open source codebases like PostgreSQL

A large increase: back-patched commits to PostgreSQL's prior stable release jumped more than 74% in a single year, and back-patches to the in-progress release rose over 60%, attributed to people using LLMs to find and report bugs. LLMs can draft fixes, but those drafts still require human review since they aren't always correct or standards-compliant.

_Anyone weighing AI-assisted bug hunting against maintainer bandwidth can follow this trend on daily.dev._

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#postgresql](https://daily.dev/tags/postgresql), [#ai-coding](https://daily.dev/tags/ai-coding)

[View this post on daily.dev](https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Postgres 19 is late, and it's AI's fault","url":"https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t"},"datePublished":"2026-10-23T05:44:03.356Z","dateModified":"2026-10-23T05:44:33.926Z","description":"PostgreSQL 19 is delayed until November because LLMs are finding bugs faster than committers can fix them, Robert Haas writes. Three major features,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d1b73fd93dfcf0b1675d8b12489041b7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d1b73fd93dfcf0b1675d8b12489041b7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Neon","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Neon","logo":"https://media.daily.dev/image/upload/s--65EDghou--/f_auto/v1724339118/logos/neontech","url":"https://daily.dev/sources/neontech"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,postgresql,ai-coding","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Neon","item":"https://daily.dev/sources/neontech"},{"@type":"ListItem","position":3,"name":"Postgres 19 is late, and it's AI's fault"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/postgres-19-is-late-and-it-s-ai-s-fault-4maw4xj9t#faq","mainEntity":[{"@type":"Question","name":"why is PostgreSQL 19 release delayed","acceptedAnswer":{"@type":"Answer","text":"PostgreSQL 19 is delayed past its usual September-October window and most likely won't ship until November because LLMs are finding bugs in the codebase faster than committers can fix and review them. Back-patched commits jumped more than 60% year over year, diverting reviewer time and forcing three major features to be reverted late in the beta period. Tracking a major database release slip? Follow PostgreSQL 19 developments as they land on daily.dev."}},{"@type":"Question","name":"which features were reverted from PostgreSQL 19 beta","acceptedAnswer":{"@type":"Answer","text":"Three major features were pulled from PostgreSQL 19 between August 27 and September 15: UPDATE/DELETE FOR PORTION OF, SQL Property Graph Queries (SQL/PGQ), and ALTER TABLE MERGE PARTITION/SPLIT PARTITION. All three were reverted late in the beta cycle, which is unusual compared to prior years' feature-freeze-adjacent reverts. Developers planning around these partition and graph query features can watch for updates on daily.dev."}},{"@type":"Question","name":"how many bugs are LLMs finding in open source codebases like PostgreSQL","acceptedAnswer":{"@type":"Answer","text":"A large increase: back-patched commits to PostgreSQL's prior stable release jumped more than 74% in a single year, and back-patches to the in-progress release rose over 60%, attributed to people using LLMs to find and report bugs. LLMs can draft fixes, but those drafts still require human review since they aren't always correct or standards-compliant. Anyone weighing AI-assisted bug hunting against maintainer bandwidth can follow this trend on daily.dev."}}]}
```

