Repository navigation
Commit after truncate to reduce lock contention - #263
Merged
Merged
Conversation
Truncate takes an `AccessExclusive` lock on the table, which blocks all other transactions from accessing the table, including select for datastore_info and any other access to the table contents. Since those operations are called from the web interface, the UI can hang for the timeout period or untill the copy finishes. This is poor user experience when dealing with large files. So, truncate in it's own transaction, so that the AccessExclusive lock is held for the least amount of time possible.
Member
|
@jqnatividad we can merge this and i will include into mine PR |
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
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.
Truncate takes an
AccessExclusivelock on the table, which blocks all other transactions from accessing the table, including select for datastore_info and any other access to the table contents. Since those operations are called from the web interface, the UI can hang for the timeout period or untill the copy finishes. This is poor user experience when dealing with large files.So, truncate in it's own transaction, so that the AccessExclusive lock is held for the least amount of time possible.