--- title: PostgreSQL 19's troubled release cycle: eight late... description: PostgreSQL 19's development cycle has been unusually chaotic: eight major features landed in the final five weeks before feature freeze, and several have since... canonical: https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: PostgreSQL 19's troubled release cycle: eight late features, multiple reverts, and a delayed GA | daily.dev og:description: PostgreSQL 19's development cycle has been unusually chaotic: eight major features landed in the final five weeks before feature freeze, and several have since... og:url: https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc og:image: https://api.daily.dev/og/posts/8miByaTzC.png og:image:alt: PostgreSQL 19's troubled release cycle: eight late features, multiple reverts, and a delayed GA 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. # PostgreSQL 19's troubled release cycle: eight late features, multiple reverts, and a delayed GA **[Collections](https://daily.dev/sources/collections)** · 4 min read · 11 upvotes · 2 comments ## Summary PostgreSQL 19's development cycle has been unusually chaotic: eight major features landed in the final five weeks before feature freeze, and several have since been reverted after post-freeze bug hunts, including SQL/PGQ graph queries, referential integrity fast-path batching, ALTER TABLE partition merge/split, and non-plain pg_dumpall formats. Still contested features include REPACK (CONCURRENTLY), online data checksums, FOR PORTION OF, and pg_get_*_ddl(). Beta 4 has slipped to September 24, 2026 with GA targeted for late October, well behind PostgreSQL 18's timeline. LLM-assisted bug hunting (Claude) is credited with catching many of these issues and is also linked to a surge past forty CVE fixes this year. Some argue the reverts show the process working as intended, and that the real problem is the April 8 feature freeze cliff encouraging last-minute feature cramming. Graph queries and other cut features are now expected to land in PostgreSQL 20 instead. ## Content PostgreSQL 19 was shaping up to be one of the biggest feature releases in years. Now it's a cautionary tale about what happens when too much lands too late. ## How we got here Eight major features landed in the final five weeks before feature freeze. That's a lot of code to review under pressure, and the beta cycle has been paying for it ever since. As of late September 2026, the team has reverted 53 features during beta — compared to roughly 44 for PG18 — and added a fourth beta release scheduled for September 24, 2026. General availability is now expected sometime in mid-to-late October, well behind the usual fall schedule. One AI-assisted readiness review gave PG19 a 4 out of 10 at this stage, noting "a critical item has a candidate patch, several high-severity items still lack patches." Confidence in that assessment: 0.83. ## What got reverted The headline losses: - **SQL Property Graph Queries (SQL/PGQ)** — one of the most anticipated features, pulled due to design flaws found after commit - **ALTER TABLE MERGE/SPLIT PARTITION(S)** — partition management improvements, gone - **GROUP BY ALL** — a convenience syntax that didn't survive post-commit review - **TOAST lz4 compression default** — reverted over correctness concerns - **UPDATE/DELETE FOR PORTION OF** — temporal range operations, pulled during beta - **Online data checksum transitions** — reverted from the stable branch due to bug risk during beta; still active on master, targeting version 20 - **Referential integrity fast-path batching** — only the per-row path remains - **Three pg_get_ddl reconstruction functions** — removed for compatibility reasons - **Identifier casefolding** — hit a locale/encoding behavior bug In a single week (September 8–16), six features were reverted across 74 commits, out of 71 total commits to the stable branch. That's a striking ratio. ## What's still expected to ship Not everything is gone. Features still on track for PG19: - **pg_plan_advice and pg_stash_advice** — two new contrib modules that let you capture a query plan as a compact string (join order, join method, scan method, parallelism) and force the planner to reproduce it later. Unlike raw EXPLAIN output, advice strings omit costs and timings, making them stable across statistics changes and diffable across versions. pg_stash_advice maps query IDs from pg_stat_statements to advice strings in shared memory, applying them transparently without application changes. Worth noting: pinning plans removes the planner's ability to adapt as data changes, so the advice is to trim these to only the decisions that matter. - **Parallel autovacuum** - **ON CONFLICT DO SELECT** - **IGNORE NULLS in window functions** - **Deeper EXPLAIN output for async I/O and prefetching** — EXPLAIN (ANALYZE, BUFFERS, IO) now surfaces more detail about asynchronous I/O behavior and prefetching, which should help diagnose I/O-bound query performance. REPACK and REPACK CONCURRENTLY are still contested, with several commits narrowing what the command accepts. ## The AI angle LLM-assisted bug hunting is a real factor here. Robert Haas ran a "scary bug contest" that surfaced several late-breaking issues. At least one contributor has been running an AI-assisted testing harness against PG19 and sending findings to the hackers mailing list — with mixed feelings about the timing. "I guess we should do it a couple of months earlier," they noted. The same dynamic appears to be behind a jump to 28 CVEs in the August 2026 PostgreSQL 18 patch release. AI-assisted security research is finding things that weren't found before, which is good, but the timing relative to release cycles is awkward. The real structural problem, though, isn't the revert process — that's working as intended. It's the April 8 feature freeze cliff that encourages a rush of late commits, which then need to be unwound during beta. ## What to do now Treat PostgreSQL 18 as the safe upgrade target for now. Watch the hackers mailing list if you're tracking specific features — the situation is still moving. And if you were counting on SQL/PGQ graph queries, start adjusting expectations: at this point, PostgreSQL 20 is looking like the release to watch. ## Questions this post answers ### Is SQL/PGQ graph query support included in PostgreSQL 19? No, SQL/PGQ graph queries were reverted from PostgreSQL 19 after being merged too close to feature freeze and hitting post-freeze bugs. Along with it, referential integrity fast-path batching, ALTER TABLE partition merge/split, and non-plain pg_dumpall formats were also reverted. These features are expected to be reconsidered for PostgreSQL 20 instead. _Track PostgreSQL 19 versus 20 feature changes on daily.dev before planning a graph-query migration._ ### When is PostgreSQL 19 GA expected to ship? PostgreSQL 19 general availability is targeted for late October, following a Beta 4 scheduled for September 24, 2026. This is notably behind PostgreSQL 18's release schedule, largely because eight major features landed in the final five weeks before feature freeze and several required reverts during post-freeze bug hunting. _Follow PostgreSQL release timelines on daily.dev to plan upgrade windows around the delayed GA._ ## Community discussion Top comments from developers on daily.dev. **@pdfopsdev** · 1 upvotes > the partition merge/split revert doesn't surprise me tbh, concurrent DML during a live split is one of the nastier correctness problems in postgres internals. imo the real bug isn't the reverts, it's cramming eight features into the five weeks before freeze every cycle. **@mdsiaofficial** · 0 upvotes > is this the is written (rust) version? ## Similar posts on daily.dev - [PostgreSQL 19 Beta Introduces SQL Graph Queries and Concurrent Table Repacking](https://daily.dev/posts/postgresql-19-beta-introduces-sql-graph-queries-and-concurrent-table-repacking-2adopzbmz) · InfoQ · 91 upvotes · 4 comments --- Tags: [#security](https://daily.dev/tags/security), [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc) ```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":"PostgreSQL 19's troubled release cycle: eight late features, multiple reverts, and a delayed GA","url":"https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc"},"datePublished":"2026-09-15T16:04:53.320Z","dateModified":"2026-09-22T02:16:42.323Z","description":"PostgreSQL 19's development cycle has been unusually chaotic: eight major features landed in the final five weeks before feature freeze, and several have since...","isAccessibleForFree":true,"articleSection":"Collections","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":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":11},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"security,database,postgresql","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"PostgreSQL 19's troubled release cycle: eight late features, multiple reverts, and a delayed GA"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc","comment":[{"@type":"Comment","text":"the partition merge/split revert doesn’t surprise me tbh, concurrent DML during a live split is one of the nastier correctness problems in postgres internals. imo the real bug isn’t the reverts, it’s cramming eight features into the five weeks before freeze every cycle.","datePublished":"2026-09-15T18:01:52.412Z","url":"https://daily.dev/posts/8miByaTzC#c-MwiVrrrXv","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"is this the is written (rust) version?","datePublished":"2026-09-15T18:24:22.683Z","url":"https://daily.dev/posts/8miByaTzC#c-I5DU07UsX","author":{"@type":"Person","name":"Md Shoriful Islam Ashiq","url":"https://daily.dev/mdsiaofficial","image":"https://avatars.githubusercontent.com/u/22385106?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/postgresql-19-s-troubled-release-cycle-eight-late-features-multiple-reverts-and-a-delayed-ga-8mibyatzc#faq","mainEntity":[{"@type":"Question","name":"Is SQL/PGQ graph query support included in PostgreSQL 19?","acceptedAnswer":{"@type":"Answer","text":"No, SQL/PGQ graph queries were reverted from PostgreSQL 19 after being merged too close to feature freeze and hitting post-freeze bugs. Along with it, referential integrity fast-path batching, ALTER TABLE partition merge/split, and non-plain pg_dumpall formats were also reverted. These features are expected to be reconsidered for PostgreSQL 20 instead. Track PostgreSQL 19 versus 20 feature changes on daily.dev before planning a graph-query migration."}},{"@type":"Question","name":"When is PostgreSQL 19 GA expected to ship?","acceptedAnswer":{"@type":"Answer","text":"PostgreSQL 19 general availability is targeted for late October, following a Beta 4 scheduled for September 24, 2026. This is notably behind PostgreSQL 18's release schedule, largely because eight major features landed in the final five weeks before feature freeze and several required reverts during post-freeze bug hunting. Follow PostgreSQL release timelines on daily.dev to plan upgrade windows around the delayed GA."}}]} ```