Repository navigation
fix: Reuse range boundaries when resuming parallel PG migration - #369
Merged
Merged
Conversation
Member
Author
|
@ihorponom Please review. |
anush008
force-pushed
the
pg-resume-boundaries
branch
from
October 11, 2026 18:45
40f382b to
9ac3bf3
Compare
ihorponom
approved these changes
Oct 12, 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
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.
Same as #353, applied to the PG vector migration.
The shared boundary and count-check code is moved into
cmd/utils.goand used by both the Qdrant and PG vector migrations.