Repository navigation
test: retain logical restore recovery loss - #30
Merged
Merged
Conversation
This was referenced Oct 27, 2026
grove
marked this pull request as ready for review
October 27, 2026 13:39
…tore-loss # Conflicts: # tests/integrations/pg-mdm/time/audit.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A real
pg_dumpandpg_restoreof a populated two-occurrence recovery fixture completes, but the restored database loses React rules, versions, activations, lifecycle events, work and attempt history while retaining MDM case and receipt vectors. The source pg_react extension has no registered dump configuration. The regression compares portable resolved role and object identities rather than assuming copied OIDs remain valid.This PR preserves the executable regression and raw evidence separately from the physical-clone repair. It does not repair logical restore or qualify release. A repair must preserve durable rows, safely rebind restored role and relation identities, and verify explicit activation and bounded resumption.
The branch merges main
f19397a6a96ea563dd0b63ac556031a98aca47c7and retains both logical-restore and physical-clone test modes. Local diagnostic runs on a separately identified non-pinned producer reached the expected logical-state assertion after successful dump/restore, and passed the physical-clone recovery check. The raw observations and an earlier setup failure are retained; these runs are not exact-artifact qualification. Python syntax, workflow syntax, documentation and whitespace checks passed. GitHub CI for the updated head is required.Refs #11 and #12.