# PostgreSQL 19 reaches RC1 but moves general availability to November 19 PostgreSQL 19 RC1 shipped October 15, but the project moved the planned GA from October 29 to November 19 so it can absorb the November maintenance fixes. The candidate includes consequential database-maintenance and replication changes that need workload testing before upgrades. RC2 is scheduled for November 12, GA for November 19. New concurrent REPACK, parallel autovacuum, replication behaviour and planner changes remain pre-release; developers should test extensions, query plans and upgrades rather than deploying the RC to production. - Status: Active - Published: 2026-10-16T06:17:15+13:00 - Updated: 2026-10-16T06:17:15+13:00 - Categories: Web Development, Cloud & Infrastructure, Deployment & DevOps, Developer Tools, Databases & Storage - Tags: database maintenance, database upgrades, PostgreSQL, replication - Canonical HTML: https://beyondthe.news/dossiers/postgresql-19-rc1-november-19-ga-repack-replication-2026 ## What changed The PostgreSQL Global Development Group released PostgreSQL 19 RC1 on October 15, 2026. It now plans a second release candidate on November 12 and general availability on November 19, superseding a September 28 plan targeting October 29. The stated reason is to incorporate the large November 12 maintenance-fix batch before GA. RC1 includes fixes since Beta 4 for concurrent REPACK, pg_plan_advice, NULL-sensitive planner optimisations, automatic logical replication, postgres_fdw statistics, parallel autovacuum and JSON COPY column naming. ## Why it matters Database operators planning autumn upgrades need to adjust release calendars and test operational changes against their own extensions and query workloads. The release is not simply a feature preview: maintenance, planner and replication semantics can affect deployment behaviour, locking, query plans and recovery. A release candidate is not a production upgrade recommendation, and the final feature set must be read from current upstream notes rather than older beta summaries. ## The schedule has shifted by three weeks PostgreSQL's September 28 developer-list message targeted October 29 GA. The October 15 RC1 announcement instead schedules RC2 for November 12 and GA for November 19 to fold in the substantial November maintenance patch batch. Both dates remain subject to further issues. ## What the release candidate fixes Upstream lists several fixes to REPACK (CONCURRENTLY), pg_plan_advice, query planning around nullable expressions, automatic logical replication with wal_level=replica, postgres_fdw statistics import permissions, parallel autovacuum and COPY(query) TO JSON column naming. These are concrete compatibility and correctness areas to exercise in test environments. ## Why operational features matter PostgreSQL 19's native concurrent REPACK and parallel autovacuum can alter how operators reclaim space and maintain busy databases. Replication improvements and WAIT/read-your-writes behaviour could simplify some application patterns. Performance and lock behaviour must still be measured under actual workload, not inferred from feature names. ## Do not assume every beta feature shipped The project reverted several planned features during Beta 4. Older previews may mention partition split/merge, temporal modifications or SQL/PGQ graph queries that are not in the current RC. Review the actual PostgreSQL 19 release notes and extension compatibility before updating migration plans. ## Upgrade testing and readiness Moving from an older major PostgreSQL version requires a major-version upgrade strategy such as pg_upgrade or dump/restore. Operators should rehearse upgrades, check extensions, indexes and query plans, validate replication behaviour and await final GA before considering production adoption. ## Key details - RC1 released October 15, 2026. - RC2 planned November 12, 2026; GA planned November 19, 2026. - September 28 schedule had targeted October 29 GA. - Delay intended to include November supported-version fixes before GA. - Fixes include concurrent REPACK, pg_plan_advice, planner, logical replication, postgres_fdw, parallel autovacuum and JSON COPY. - Major-version upgrade process required; RC not recommended for production. ## Builder takeaways - Move PostgreSQL 19 upgrade plans from the old October 29 target to the current November 19 provisional date. - Test against RC1 in staging, including extensions, maintenance commands and replica behaviour. - Audit planned features against current release notes; some beta features were reverted. - Check query-plan regressions and operational defaults with representative data. - Keep production clusters on supported stable releases until final GA and validation. ## What to watch - November 12 RC2 changes and any new release blockers. - Final November 19 GA decision. - Extension support and compatibility reports. - Performance and correctness outcomes for REPACK, autovacuum and logical replication. ## Uncertainties - The November 19 date is planned and may change if release blockers appear. - Performance gains and operational tradeoffs vary by workload. - Current RC functionality can still receive bug fixes before GA. ## Sources - [PostgreSQL 19 RC 1 Released!](https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/) — PostgreSQL Global Development Group · primary release announcement · 2026-10-15T00:00:00+13:00. New dates, rationale and concrete RC fixes. - [PostgreSQL 19 Open Items](https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items) — PostgreSQL Wiki · primary release tracker. RC1, RC2, GA dates and open issues. - [PostgreSQL 19 RC1 and GA release dates](https://www.postgresql.org/message-id/915517c4-d0ee-49f9-bbeb-c683ef2b9d3f%40postgresql.org) — PostgreSQL Developers Mailing List · primary earlier schedule · 2026-09-28T00:00:00+13:00. Shows earlier October 29 GA target. - [PostgreSQL 19 RC1: upgrades to watch](https://www.linuxcompatible.org/story/postgresql-19-rc1-released-native-repack-parallel-autovacuum-and-upgrades-to-watch/) — LinuxCompatible · independent technical analysis · 2026-10-15T00:00:00+13:00. Operational feature context and reverted beta features; confirm against upstream.