-
Notifications
You must be signed in to change notification settings - Fork 4.1k
concurrency: integrate lock Modes in the lock table #102210
Copy link
Copy link
Closed
Labels
A-read-committedRelated to the introduction of Read CommittedRelated to the introduction of Read CommittedC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-kvKV TeamKV Team
Description
Is your feature request related to a problem? Please describe.
We introduced the concept of lock.Modes in #96026. Lock modes encapsulate all the information required to perform conflict resolution between any 2 locks.
Today, the lock table uses SpanAccess information in conjunction with the timestamp at which a lock is held to perform conflict resolution. The concept of SpanAccess doesn't extend to SHARED locks. We should instead switch to constructing and using lock.Modes to perform conflict resolution.
Jira issue: CRDB-27341
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-read-committedRelated to the introduction of Read CommittedRelated to the introduction of Read CommittedC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-kvKV TeamKV Team