An ultimate guide to upgrading your PostgreSQL installation
summary
Gives concrete upgrade choices and actionable steps: use pg_dump -Fc or -Fd --jobs for reliable dump/restore (practical cutoff: several hundred GB), use pg_upgrade --link to minimize downtime but accept high risk with hard links, or set up logical replication/Slony to migrate with near-zero downtime. Reminds to run analyze_new_cluster (or parallel ANALYZE) because statistics do not carry over, checkpoint before stop, pause pgBouncer rather than drop connections, verify locales, test extensions and packages, read release notes and rehearse on staging with backups.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:23Why upgrade
- 2:47Do not upgrade
- 4:48Version number
- 5:40Types of upgrades
- 6:59General approaches
- 9:17Minor upgrades
- 10:27Major upgrades
- 13:23Checking packages
- 14:49Methods of upgrade
- 15:25PGDump
- 19:54PGDump procedure
- 22:36Outline
- 23:19How it works
- 25:40Outline how it works
- 26:03How to proceed
- 27:05How to minimize downtime
- 29:49Hot standby replicas
- 33:50PostgreSQL upgrade cluster
- 35:26Extensions
- 36:36Replication
- 38:23Logical Replication
- 40:12Slow Replication
- 41:05Disclaimer
- 41:41Conclusion
- 43:09Useful links
- 44:16Questions
related talks
50mAn ultimate guide to upgrading your PostgreSQL installation
26mMastering Large-Scale PostgreSQL Migration
01h 01mAlways Online or Bust
01h 41mPostgreSQL Upgrades with Logical Replication & Minimal Downtime
32mPostgreSQL The Hard Way
59mPostgreSQL Don'ts and Dos
49mKeeping Up with the Times, or How to Upgrade PostgreSQL
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success