PostgreSQL Upgrades with Logical Replication & Minimal Downtime
summary
Walks through upgrading PostgreSQL 13→17 by creating per-table publications and a subscription, copying schema and globals with pg_dump, and using pgBackRest for separate backups; logical replication handles most row changes but large objects are excluded and sequences must be manually advanced before cutover. Requirements include replication slots, suitable replica identity or primary keys, enough parallel workers and increased timeouts for long transactions. Demo completes a live cutover in about four to five minutes and can be scripted down to two.
AI-written summary · about
chapters (12)
- 0:00PostgreSQL upgrades intro
- 3:37Planning production upgrades
- 7:29Logical replication suitability
- 10:37Tables without primary keys
- 16:20Config changes before replication
- 22:45Publication and subscription setup
- 35:16Deployment plan step-by-step
- 50:55Target system config
- 1:06:35Logical replication demo
- 1:13:57Failover and sync
- 1:20:43Testing and completing upgrade
- 1:21:52Q&A: Logical vs dump/restore
related talks
50mAn ultimate guide to upgrading your PostgreSQL installation
36mHow to Upgrade Replication Clusters without Downtime?
53mThe journey towards active replication in PostgreSQL
41mOnline Upgrade of replication clusters without downtime
46mAn ultimate guide to upgrading your PostgreSQL installation
32mPostgreSQL Major Upgrades: Swapping the Elephant Without Breaking the Room
51mSpeeding up logical replication setup
31mPast, Present, and Future: Logical Decoding and Replication in PostgreSQL