End Of Life Is Not the End
summary
Postgres major versions ship yearly and get five years of support so Postgres 13 has EOL this year; remaining on EOL risks no CVE patches, compliance failures, and extra RDS extended‑support costs. Upgrade paths: pg_upgrade (use --check, increase --jobs, choose link vs no‑link), pg_dump/restore for <~100GB, or logical replication/blue‑green for near‑zero downtime. Plan for double the storage for pg_upgrade, confirm extension compatibility, and run ANALYZE after major upgrade to restore optimizer stats. RDS now can concurrently upgrade primary and replicas.
AI-written summary · about
chapters (9)
- 0:00PostgreSQL end of life intro
- 1:04PostgreSQL versioning lifecycle
- 3:57End of life meaning
- 9:42Risks of not upgrading
- 19:38Major vs minor upgrades
- 27:57Upgrade strategies
- 36:14Cloud-native upgrades
- 46:11Real-world upgrade issues
- 48:20Call to action
related talks
52mWill Postgres Live Forever?
32mPostgreSQL Major Upgrades: Swapping the Elephant Without Breaking the Room
50mAn ultimate guide to upgrading your PostgreSQL installation
14mEDB & Postgres through the years and in the years to come
46mAn ultimate guide to upgrading your PostgreSQL installation
49mKeeping Up with the Times, or How to Upgrade PostgreSQL
23mFuture Postgres Challenges
46mWill Postgres Live Forever?