The PostgreSQL Global Development Group has moved the targeted general availability date for PostgreSQL 19 from late September to November 19, 2026. The delay follows late-cycle code reviews using large language model tooling that surfaced roughly 40 defect reports, prompting core maintainers to revert between 8 and 10 major features slated for the release.
Reverted Features and Architectural Defect Findings
According to PostgreSQL committer and EDB vice president Peter Eisentraut, automated LLM code review tools surfaced structural design problems alongside a long tail of edge-case bugs that had passed initial human review. Addressing the volume of findings within the final beta cycle created an unmanageable triage burden, leading maintainers to pull affected patches rather than risk shipping unverified fixes.
Among the features reverted from PostgreSQL 19 and postponed to PostgreSQL 20:
- SQL Property Graph Queries (SQL/PGQ)
GROUP BY ALLsyntax support- Partition merge and split utility commands
Eisentraut noted that the underlying patches were written and submitted before modern LLM code review tools became widely capable, effectively subjecting older contributions to an elevated, retroactive quality standard during late beta testing.
Features Retained for PostgreSQL 19
Despite the feature rollbacks, PostgreSQL 19 retains several core engine improvements slated for the November release candidate and GA rollout:
REPACK (CONCURRENTLY)table restructuring- Logical replication support for sequences
- Query planner guidance via
pg_plan_advice - Parallel autovacuum optimizations
- JSON format support for
COPY (query) TOcommands
The PostgreSQL maintainers expect the postponed features to be reworked, validated against current automated review pipelines, and reintroduced during the PostgreSQL 20 development cycle.
