storage: ignore {exclusive,shared} locks in ScanConflictingIntentsForDroppingLatchesEarly #110830
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.
ScanConflictingIntentsForDroppingLatchesEarly is called by non-locking read requests to check for conflicts before evaluating. Non-locking reads do not conflict with Exclusive or Shared locks -- so these can be ignored when scanning the lock table. This patch does so, by making use of an appropriately configured
LockTableIterator
.Informs #100193
Release note: None