How vasyakrg/pgdump-s3 works
This repository packages a PostgreSQL backup and restore script. The main workflow selects databases, creates dumps, stores them locally or in S3, and applies retention; scheduled runs use cron. Restore reads selected backups, restores databases, and can run post-restore SQL. The README also documents role backups, multiple dump formats, compression, and success healthchecks. The tree shows backup.sh and SQL directories, but no source excerpts were provided, so relationships below rely on README statements rather than inspected implementation; internal call details remain unverified.
Main entry points: backup.sh Backup and restore runner · post-restore Post-restore SQL
Components 12
Backup
- Backup and restore runner
backup.sh - Dump selection and formats
backup.sh - Role dump
backup.sh
Storage
- Local or S3 storage
backup.sh - Backup rotation
backup.sh
Restore
- Restore selection
backup.sh - Database restore
backup.sh - Post-restore SQL
post-restore
Operations
- Healthchecks service
Other components
- Operator
- Cron scheduler
- PostgreSQL
Connections 13
- Operator → Backup and restore runner: starts manually
README.md - Cron scheduler → Backup and restore runner: starts scheduled
README.md - Backup and restore runner → Dump selection and formats: selects and dumps
README.md - Dump selection and formats → PostgreSQL: reads databases
README.md - Backup and restore runner → Role dump: optionally dumps roles
README.md - Backup and restore runner → Local or S3 storage: stores backups
README.md - Backup and restore runner → Backup rotation: rotates backups
README.md - Operator → Restore selection: selects restore
README.md - Restore selection → Local or S3 storage: reads backups
README.md - Restore selection → Database restore: chooses databases
README.md - Database restore → PostgreSQL: restores databases
README.md - Database restore → Post-restore SQL: runs scripts
README.md - Backup and restore runner → Healthchecks service: sends success check
README.md