feat(api): add endpoint for pg-pg source and destination row count check#4556
Merged
Conversation
Amogh-Bharadwaj
force-pushed
the
pg-row-check
branch
from
cb24492 to
b620841
Compare
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
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
2 participants
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.
Why
This is useful for validating mirror correctness after initial load and zero-lag CDC for PG - PG mirrors.
What
What the endpoint does
User can pick a selection of tables to validate counts for.
Counts for source and destination obtained via two goroutines.
For tables greater than 10GB -- gets an approximate row count as counts can take a long time
For tables lesser than 10GB -- gets exact count
Count times capped to 30 seconds for each table. Response structure denotes what the counts are and whether they're approximate
Functionally tested