Use object-level locks for concurrent grants to improve parallelism #595
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
Replace database-wide locks with hash-based object locks. Enables parallel grant operations on different objects while preventing catalog conflicts. Uses hashtext() for deterministic lock IDs like "grant:table:db.schema.table". Signed-off-by: Benoit Tigeot <[email protected]>
benoittgt
commented
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Replace database-wide locks with hash-based object locks. Enables parallel grant operations on different objects while preventing catalog conflicts.
Uses
hashtext()for deterministic lock IDs like "grant:table:db.schema.table".I used a small script to test conflicts: https://gist.github.com/benoittgt/8b9b9b305dc961308380be865a1ce66a
This is another extended version of #520