chore: add PGLocks query to analyze what locks are held in pg #15308
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.
Adds
PGLocks
query similar to how we havePing()
. I cannot do this via SQLc, as SQLc does not know aboutpg_locks
table.The string format is able to be changed to extract more value. I recognize this is not perfect, but I wrote it trying to learn more about these locks. It felt valuable enough to keep. Not all values are handled correctly here, I'll add functionality as required.
Some example output
serializable
and runGetQuotaConsumedForUser()
UpdateWorkspaceBuildCostByID
in the TXSpecifically these are the new locks aquired:
Used to respond here: #15261 (comment)