2014
DOI: 10.1007/s00778-014-0359-9
|View full text |Cite
|
Sign up to set email alerts
|

Distributed snapshot isolation: global transactions pay globally, local transactions pay locally

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

2
30
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 26 publications
(32 citation statements)
references
References 24 publications
2
30
0
Order By: Relevance
“…By maintaining multiple data versions, TxCache [49] ensures that a transaction always reads from a consistent snapshot regardless of whether each read operation comes from the database or the cache. Binning et al [7] show how only distributed snapshot transactions pay the cost of coordination. Serial Safety Net (SSN) [65] is able to make any concurrency control protocol to support serializability by detecting dependency cycles.…”
Section: Related Workmentioning
confidence: 99%
“…By maintaining multiple data versions, TxCache [49] ensures that a transaction always reads from a consistent snapshot regardless of whether each read operation comes from the database or the cache. Binning et al [7] show how only distributed snapshot transactions pay the cost of coordination. Serial Safety Net (SSN) [65] is able to make any concurrency control protocol to support serializability by detecting dependency cycles.…”
Section: Related Workmentioning
confidence: 99%
“…These data anomalies were reported in the 1990s and before. In recent years, there still exist extensive research works that focus on reporting new data anomalies, including Aborted Reads [42], Intermediate Read [2,42], Read-only Transaction Anomaly [25,40], Serial-concurrency-phenomenon and Cross-phenomenon [12]. [16] reports Long Fork, Fractured Reads, and Causality Violation.…”
Section: Related Workmentioning
confidence: 99%
“…Dirty Write and Dirty Read are able to be categorised as single-variable data anomalies based on our framework. Read Skew, Write Skew, together with our proposed Read-Write Skew, Write-Read Skew and Double-Write Skew, are originally proposed in [2,6] between two transactions, and are extended to three or more transactions in [4,12,16,24,25,34].…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations