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.
Resolves #6755
Resolves #6734
Motivation
Currently we are using
FOR UPDATE
locks in every lock queries, but there is no need to use this lock type for queries that are not going to delete or modify primary key. In these cases it's better to useFOR NO KEY UPDATE
to avoid unnecessary locks.Also, there are several locks that hold data not meant to be updated.
Changelog
FOR UPDATE
toFOR NO KEY UPDATE
for queries that are not going to delete data or modify PKBlocks
andCurrentTokenBalances
runners to update token holders function since this lock is only needed for insert orderingEmptyBlockSanitizer
so it doesn't conflict with general block fetchers