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 state. A restored backup lost all data since the snapshot. Switches to the coop-cloud /pg_backup.sh convention (as matrix-synapse): backup = pg_dump|gzip; restore = terminate connections, FORCE-drop, recreate, reimport. Caught + validated by the cc-ci recipe CI loop (a seeded marker now survives backup→restore).
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 state. A restored backup lost all data since the snapshot. Switches to the coop-cloud `/pg_backup.sh` convention (as matrix-synapse): backup = pg_dump|gzip; restore = terminate connections, FORCE-drop, recreate, reimport. Caught + validated by the cc-ci recipe CI loop (a seeded marker now survives backup→restore).
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.
@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 state. A restored backup lost all data since the snapshot. Switches to the coop-cloud/pg_backup.shconvention (as matrix-synapse): backup = pg_dump|gzip; restore = terminate connections, FORCE-drop, recreate, reimport. Caught + validated by the cc-ci recipe CI loop (a seeded marker now survives backup→restore).@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
!testme
🌻 cc-ci —
mattermost-lts@4ca7f418✅ passedfull logs · dashboard
autonomic-bot referenced this pull request2026-06-19 03:49:29 +00:00
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.