PostgreSQL Backup Strategies
summary
Replication does not replace backups: a real outage once nukes 5,000 VMs and takes months to recover. Concrete options: pg_dump (custom format) for logical backups (single-threaded, use compression level ~3–5, restore with pg_restore and optional parallel -j), pg_basebackup + WAL archiving for fast physical restores and PITR, use pg_receivexlog or archive_command to ship 16 MB WAL segments, and never forget fsync when speeding restores — turning it off helps performance but risks silent corruption. Test restores regularly.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:30Replication and Clustering
- 2:50Backup Planning
- 3:29Performance Impacts
- 5:43Logical Backups
- 12:18Formats
- 15:09PGDump
- 18:16Compression
- 21:21SSH Compression
- 22:19PG Restore
- 25:24Parallel PG Restore
- 27:32FSync
- 29:33PG Dump All
- 30:58PG Dump Limitations
- 33:37Snapshots
- 34:58Online Backups
- 37:02PostgreSQL Base Backup
- 38:58PostgreSQL Low Dark
- 43:08PostgreSQL Base Backups
- 44:48PostgreSQL Base Backup Impacts
- 47:31Backup Strategies
- 49:12Backup Retention
- 51:20Backup vs Replication
- 51:59Lag behind replicas
- 53:02Test your backups
related talks
50mPostgreSQL Backup and Recovery Methods
22mPostgreSQL Disaster Recovery Fundamentals
59mPostgreSQL Don'ts and Dos
49mTools for Creating PostgreSQL Backups
51mHeavy Duty Backup w/PgBackRest
49mWhat can't pgBackRest do for you?
38mScaling PostgreSQL Replicas Under Load
29mYou Don't Need a Database Backup Policy