Add history table indexes for RDE generation - #3206
Merged
Merged
Conversation
weiminyu
approved these changes
Aug 10, 2026
weiminyu
left a comment
weiminyu
left a comment
Collaborator
There was a problem hiding this comment.
@weiminyu reviewed 4 files and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on gbrodman).
gbrodman
enabled auto-merge
August 10, 2026 20:58
We can make the "select the correct most recent history object" query much more efficient + simple but we'll want to have these indexes so we can select the most recently modified entry for a given repo ID (at least, one before a particular watermark).
gbrodman
force-pushed
the
historyIndexes
branch
from
August 12, 2026 15:50
f830b5f to
932b434
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 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.
We can make the "select the correct most recent history object" query much more efficient + simple but we'll want to have these indexes so we can select the most recently modified entry for a given repo ID (at least, one before a particular watermark).
This change is