docker-postgres-backup-local
docker-postgres-backup-local copied to clipboard
Backup PostgresSQL to local filesystem with periodic backups and rotate backups.
I leave an example of a small DB:  The last backup is with the new configuration and, as can be seen, it increases the size by 166%.  Then...
I'd like to have an option to check the last backup and if its the same, then discard the current one. It saves a bit of space, and it will...
I was wondering if through a Dockerfile or other means if there was a way to change the UID/GID mappings of the postgres user/group?
It would be nice to check backup errors and monitor backup status to healthchecks.io in cloud or self-hosted using curl or wget. [https://stackoverflow.com/questions/6341321/how-to-check-if-postgresql-backup-was-successful](https://stackoverflow.com/questions/6341321/how-to-check-if-postgresql-backup-was-successful) [https://healthchecks.io/docs/bash/](https://healthchecks.io/docs/bash/) [https://healthchecks.io/docs/signaling_failures/](https://healthchecks.io/docs/signaling_failures/)
Is there any reason not to use [pigz](https://zlib.net/pigz/)? It's an apt-get install away, it's perfectly gzip compatible, and it's multi-core so vastly faster.
Updated script to take advantage of functions and for loops to clean up the code
I accidentally configured backups to a folder which was a SMB mount on my linyux box. And the backups ran, but of course at the end of the script it...
I have this variables set to 0 BACKUP_KEEP_WEEKS | Number of weekly backups to keep before removal. Defaults to 4. BACKUP_KEEP_MONTHS | Number of monthly backups to keep before removal....
Allow to disable the gzip compression when using cluster mode YES and better document the cluster mode. Reported by @JohnTheNerd: > [...] I think what tripped me up is that...
no file backuped, the container logs ``` stderr: 2024/08/24 18:00:28 Running version: v0.0.10 stderr: 2024/08/24 18:00:28 new cron: @weekly stderr: 2024/08/24 18:00:28 Opening port 8085 for health checking stderr: 2024/08/25...