Beyond PostgreSQL 17
summary
Seven concrete DBA workarounds for Postgres 17 are described: native logical replication now preserves replication slots so you can perform near zero downtime major upgrades (common downtime example given as 8 hours), but schema changes still require care; PL/pgSQL_check generates dependency trees and finds syntax/security issues; PG squeeze runs online VACUUM FULL as a background worker; EDB Postgres tuner recommendations and TPA automate tuning and provisioning; PG cron stores jobs in‑DB; clone_schema handles renamed schema clones.
AI-written summary · about
chapters (9)
- 0:00PostgreSQL 17 limits and fixes
- 6:59Zero-downtime upgrades with logical replication
- 19:48Schema change validation
- 27:19Automated tuning with TPA
- 35:44Online vacuum full
- 40:00Workload reports for performance
- 41:06Job scheduling with pg_cron
- 43:10Schema cloning in multi-tenant
- 46:46Q&A
related talks
43mPostgreSQL 17 and beyond
50mAn ultimate guide to upgrading your PostgreSQL installation
46mPostgres Platform "Best Practices" for the Modern DBA
51mWhen Postgres Can't, You Can!
11mThe Seven Principles for Making a PostgreSQL DB Work Fast
46mPostgreSQL 16 and beyond
36mPostgreSQL: Ups, DevOps...
14mEDB & Postgres through the years and in the years to come