fix(backup): reimport the postgres dump on restore (restore was a no-op)
cc-ci/testme cc-ci: success

The recipe dumped the DB on backup but shipped NO backupbot.restore.post-hook, and
archived the whole live PGDATA dir — so a restore extracted files under the running
postgres without reloading them, silently keeping the un-restored (live) state. A
restored backup therefore lost all data written since the snapshot.

Switch to the coop-cloud /pg_backup.sh convention (as matrix-synapse): backup =
pg_dump|gzip -> backup.sql; restore = terminate connections, FORCE-drop, recreate,
reimport the dump deterministically. Archive just backup.sql, not the whole PGDATA dir.
This commit is contained in:
autonomic-bot
2026-05-30 00:38:44 +00:00
parent 41c9eb8e5f
commit 4ca7f4182d
3 changed files with 44 additions and 3 deletions
+2
View File
@@ -1,2 +1,4 @@
export ABRA_MATTERMOST_ENTRYPOINT_VERSION=v2
export BUSYBOX_VERSION=v1
export PG_BACKUP_VERSION=v1