Commit Graph

4 Commits

Author SHA1 Message Date
4ca7f4182d fix(backup): reimport the postgres dump on restore (restore was a no-op)
All checks were successful
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.
2026-05-30 00:38:44 +00:00
2f94930db2 chore: publish 2.1.0+10.11.6 release 2025-11-13 10:10:55 +01:00
177d5a858f chore: publish 2.0.6+10.5.12 release 2025-10-16 11:24:15 +02:00
9a716f7303 0.1.0 rc, still testing that one 2023-06-06 15:35:52 +02:00