PostgreSQL 19 RC 1 is out and GA is set for 19 November: what the late reverts mean
Victoria Shinder3 min readThe PostgreSQL Global Development Group released PostgreSQL 19 RC 1 on 15 October 2026. The announcement sets the date for general availability: 19 November 2026, unless an issue requires a further delay or another release candidate. The project's roadmap page had planned the release for October. This piece looks at why the schedule moved and what that means for anyone planning an upgrade.
Why there is an RC 2. The announcement gives a concrete reason. The next scheduled update release for supported branches, on 12 November, will include a large number of fixes, and the release team decided to put those fixes into PostgreSQL 19 before it becomes generally available. So RC 2 will come out on 12 November, the same day as the update release, and GA follows a week later. Upgrading from earlier versions still requires a major-version method such as pg_upgrade or dump and restore.
What was fixed during Beta 4. The RC 1 notes list several fixes for REPACK (CONCURRENTLY), for pg_plan_advice, for new planner optimisations that rely on whether an expression can be NULL, for automatic enabling of logical replication when wal_level is replica, and for parallel autovacuum. postgres_fdw statistics import now runs as the owner of the foreign table, and COPY (query) TO ... (FORMAT json) now uses the query's column names, including aliases, as JSON keys.
The reverts. The bigger story of this cycle came a week earlier. On 9 October, Peter Eisentraut, a long-time PostgreSQL committer, wrote that "about 8 to 10 significant features" had been reverted from the 19 branch after beta began, some of them late, against a usual expectation of perhaps one per cycle. He offers several explanations and says the mix differs per feature:
- some features had significant architectural defects that could not be fixed quickly during beta;
- alongside them came a long tail of relatively harmless edge-case bugs that, in his words, would once have surfaced over five years; LLM-assisted code review now finds them quickly, "and then you're staring at a list of like forty defect reports";
- many senior developers spent April to August on security fixes, so beta review and testing picked up late;
- PostgreSQL's "everything works with everything" design makes some features very hard to test by hand, and he suggests LLM-assisted fuzzing should become part of feature development.
He stresses that the reverted code was written well before "vibe coding" was possible. The project chose to keep to its schedule rather than delay for more fixes, and is still discussing a way to commit features with an "experimental" status.
What still ships. Eisentraut names REPACK CONCURRENTLY, logical replication of sequences and planner hinting with pg_plan_advice among the headline items, and expects the reverted features to return, several of them in PostgreSQL 20. For operators the practical reading is simple: plan testing against RC 1 now, and treat RC 2 on 12 November as the build to validate before a GA upgrade.
Sources: PostgreSQL Global Development Group, "PostgreSQL 19 RC 1 Released!" — https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/ ; Peter Eisentraut, "The reverts will continue until morale improves" — https://peter.eisentraut.org/blog/2026/10/09/the-reverts-will-continue-until-morale-improves