Skip to content

kv: establish new read snapshot on statement boundaries under RC #100133

Closed
#104362
Closed
kv: establish new read snapshot on statement boundaries under RC#100133
#104362
Assignees
crl-ghost
Labels
A-kv-clientRelating to the KV client and the KV interface.A-kv-transactionsRelating to MVCC and the transactional model.A-read-committedRelated to the introduction of Read CommittedC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)P-0Issues/test failures with a fix SLA of 2 weeksT-kvKV Team
@nvb

Description

@nvb
nvb
opened on Mar 30, 2023

With the introduction of the read committed isolation level, transactions running under the isolation level will establish a new read snapshot on each statement boundary. This should live in Txn.Step/TxnCoordSender.Step.

cockroach/pkg/kv/kvserver/concurrency/isolation/levels.proto

Lines 93 to 95 in f9ac216

// Read Snapshot Scope: Does the isolation level allow transactions to operate
// across multiple read snapshots? If not, a single read snapshot is used for
// the entire transaction. If so, what is the scope of each read snapshot?

Jira issue: CRDB-26578

Metadata

Metadata

Assignees

Labels

A-kv-clientRelating to the KV client and the KV interface.A-kv-transactionsRelating to MVCC and the transactional model.A-read-committedRelated to the introduction of Read CommittedC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)P-0Issues/test failures with a fix SLA of 2 weeksT-kvKV Team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions