Repository navigation
Conversation
This was referenced Oct 20, 2026
Open
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.
Read-model backfills could hold a maintenance write indefinitely under load. Bound each batch with an operator-respecting statement timeout, roll back cancelled work without losing the session lock, and shrink genuinely expensive ranges before retrying. Keep upstream duty-cycle pacing, custom plans and statistics initialization.
A cycle deadline shortened by the remaining budget now yields without shrinking the next cycle’s batch. The preview exposed this distinction: treating a nearly expired cycle as a large-batch failure eventually reduced the range to one ID. The new PostgreSQL regression fails before the correction and passes afterward; existing timeout rollback, real shrink and paced-fill tests pass as well.
Rebased by merge onto current dev
a51d950. Full query/schema behavior and retention are unchanged. Local unit checks and five focused PostgreSQL checks pass; current CI validates the exact head. Dev/dev1 deployment is still on the operator’s hold.