Parse restore error tolerance from pgcopydb log#39
Merged
teknogeek0 merged 1 commit intomainfrom Apr 14, 2026
Merged
Conversation
pgcopydb supports --restore-tolerance (default 10) but the status script always compared against a hardcoded 10. Now parses the actual tolerance value from pgcopydb's log output.
0b81c0a to
ed73b00
Compare
DmitriiAn
approved these changes
Apr 14, 2026
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.
Summary
check-migration-status.shhardcoded a tolerance of 10 for pg_restore errors, but pgcopydb supports--restore-tolerance Nto set this dynamically"within tolerance of N"or"tolerance: N"), falling back to 10 if not found