Repository navigation
fix: fence PostgreSQL named queues before claiming work - #375
Merged
Merged
Conversation
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.
PostgreSQL named-queue polls could select captured or retired work before healthy rows and fail the entire poll. They could also issue a lease for a quarantined native relay. Both global and tenant selectors now exclude those source states before LIMIT, matching the other worker claim paths.
Expanded six existing regression fixtures to PostgreSQL and encrypted PostgreSQL. All 12 new PostgreSQL cases reproduced on main before the fix; the blocked rows remain pending at epoch zero after the fix.
Validation: reproduced all 12 PostgreSQL failures independently on main before the fix. Afterward, all 205 source-cut tests and 96 worker issuance tests passed with required real PostgreSQL and plain/encrypted SQLite/PostgreSQL coverage. Strict storage lint for all targets and workspace formatting also passed.