mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #111] Feature request -- Restore from uploaded backup file #92
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#92
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 @kamasylvia on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/111
This morning, my Postgres database crashed, and I couldn't access it, including the pgbackweb table. The pgbackweb web service also stopped, so I was unable to restore my database. Fortunately, I had a previous backup stored in S3. To my surprise, I found that even if I deployed a new pgbackweb service, I still couldn't directly restore my database from S3 because it can't restore from an uploaded backup file (no upload function). I would like to ask whether the current version of pgbackweb can restore the database by uploading the previously stored backup file. If not, please add the function of uploading the backup and restoring the database.
@eduardolat commented on GitHub (Mar 31, 2025):
Good idea
@cachho commented on GitHub (Apr 1, 2025):
this is a must, not only for lost databases, but also for migrations.
@JoshuaNitschke commented on GitHub (Aug 4, 2025):
👍🏻