The PostgreSQL Global Development Group released PostgreSQL 19 Release Candidate 1 on October 15, 2026, making a near-final build available for testing. RC1 will be largely identical to the initial general-availability release, with a second release candidate scheduled for November 12, 2026 to include a large set of fixes planned for the next update; general availability is scheduled for November 19, 2026 unless further issues require delay. The release team opted to fold many upcoming update fixes into the RC cycle to minimize changes at GA.
Upgrading to PostgreSQL 19 RC1 requires a major-version migration using pg_upgrade or pg_dump/pg_restore; upgrade documentation is provided in the PostgreSQL 19 docs. Significant fixes since Beta 4 include corrections for REPACK (CONCURRENTLY) and pg_plan_advice, several fixes to new planner optimizations tied to NULLability, a fix for automatic logical replication enablement when wal_level is set to replica, a change so postgres_fdw statistics import runs as the foreign-table owner, several parallel-autovacuum fixes, and a correction so COPY (query) TO ... (FORMAT json) uses the query’s column names (including aliases) as JSON keys. A detailed list of fixes and open issues is available on the open-items page.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.