-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: non-locking reads ignore exclusive locks #94729
Copy link
Copy link
Closed
Labels
A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.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)P-0Issues/test failures with a fix SLA of 2 weeksIssues/test failures with a fix SLA of 2 weeksT-kvKV TeamKV Team
Description
See #49684 for context. If we differentiate between exclusive locks and intents, then we don't need non-locking reads to wait on exclusive locks. See also this document.
Before we do this, we'll likely want something like #91417. This was also described in #49684 (comment).
Jira issue: CRDB-23103
Epic CRDB-26544
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.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)P-0Issues/test failures with a fix SLA of 2 weeksIssues/test failures with a fix SLA of 2 weeksT-kvKV TeamKV Team