Repository navigation
Conversation
Ordering by id walks the whole table to find rows past the cutoff. Ordering by date_added pages on (date_added, id), which the new sentry_commit index range-scans directly.
github-actions
Bot
added
the
Scope: Backend
ldelvoye
marked this pull request as ready for review
November 12, 2026 00:55
This branch has not been deployed
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.
resolves INFRENG-1014
Orders the Commit cleanup scan by date_added, so it pages on (date_added, id) through the index from #130862 instead of walking the whole table by id.
Don't merge until #130862's post-deployment migration has run in every region: without the index, ordering by date is slower than today.