Ensuring High Availability in Self-Managed PostgreSQL with Patroni
summary
Three demos show a concrete path from manual backups to automated failover: a single-node backup using wal-g to S3, a three-node streaming setup built with pg_basebackup, replication slots and manual promotion plus pg_rewind for reintegration, and a Patroni cluster using Patroni with etcd where patronictl flips from async to synchronous, automatic leader election promotes a standby and pg_rewind restores the old primary — the three-node automatic failover and recovery succeed in the demo.
AI-written summary · about
chapters (12)
- 0:00Introduction to PostgreSQL high availability
- 1:05RTO and RPO for HA
- 4:15Physical replication basics
- 6:03WAL shipping to S3 demo
- 8:08Streaming replication setup
- 13:30Multi-AZ streaming demo
- 23:40Native HA limits
- 25:13Patroni for automated HA
- 31:16Patroni architecture
- 32:01Patroni config & failover demo
- 38:24Patroni benefits
- 38:48Q&A
related talks
50mPatroni Deployment Patterns
55mHigh Availability with PostgreSQL and Pacemaker
41mProtecting your data with Patroni and pgBackRest
36mDesigning Layered High‑Availability Architectures for PostgreSQL on a Budget
02h 26mTutorial
22mSecuring Postgres with streaming replication
50mThe Immortal Postgres Web
57mReliability features in Postgres Pro