mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 13:45:54 +03:00
[GH-ISSUE #125] Backup all databases #103
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BoKKeR on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/125
I understand that this might be more of a homelab feature request than production. Its unlikely that many databases are created in prod
Currently this tool can only backup the SINGLE database which is set in the connection string.
Its not unusual for me to add multiple databases to one postgresql, with this approach I will have to go each time and add a new target database.
I would much more prefer to be able to set a
wildcard *and have the tool resolve all databases and back them up each.Similarly how borgmatic does it https://torsion.org/borgmatic/docs/how-to/backup-your-databases/
Current collection of databases. Most are also created using a pginit container. Adding them to this tool becomes another task. Then updating all the cron jobs, updating all the alerts. Its error prone
Similarly the webhook alerts, from the programming perspective it makes sense to set alerts one by one, but from the users perspective, I want alerts for every database.
@empeekdev commented on GitHub (Aug 18, 2025):
+1
@softwaretirol commented on GitHub (Oct 14, 2025):
+1
@ShlomiPorush commented on GitHub (Jan 20, 2026):
+++1