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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
--offsetis used across batches, ordering only bycreated_atis not deterministic for indexed documents that share the same timestamp, which can happen with bulk imports using thecreated_at default now()column. Postgres is free to return tied rows in different orders between invocations, so--limit 100 --offset 100can skip or reprocess documents. Add a unique secondary order, such asid, before applying.range(...)so paginated classifier runs walk a stable sequence.Useful? React with 👍 / 👎.