1986
DOI: 10.1007/3-540-17187-8_36
|View full text |Cite
|
Sign up to set email alerts
|

Update serializability in locking

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
16
0

Year Published

1987
1987
2018
2018

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(16 citation statements)
references
References 15 publications
0
16
0
Order By: Relevance
“…Update serializability was introduced by Garcia-Molina and Wiederhold [4], then later extended for abort transactions by Hansdah and Patnaik [5]. US provides the same guarantees as SER for update transactions, i.e., update transactions are serialized.…”
Section: Related Workmentioning
confidence: 97%
See 1 more Smart Citation
“…Update serializability was introduced by Garcia-Molina and Wiederhold [4], then later extended for abort transactions by Hansdah and Patnaik [5]. US provides the same guarantees as SER for update transactions, i.e., update transactions are serialized.…”
Section: Related Workmentioning
confidence: 97%
“…Therefore, several previous works aim at designing consistency criteria that both provide meaningful guarantees to the application, and scale well [4][5][6][7][8][9][10][11]. At one end of the spectrum, strict serializability (SSER) ensures that transactions are atomic, and thus offers the strongest concurrency semantics.…”
Section: Introductionmentioning
confidence: 99%
“…Update serializability (US) was introduced by GarciaMolina and Wiederhold [51], then later extended to aborted transactions by Hansdah and Patnaik [52]. US guarantees that update transactions are serialized, and that read-only transactions see consistent but non-monotonic snapshots.…”
Section: Update Serializabilitymentioning
confidence: 99%
“…In the following we present their formal specifications. US was originally defined by the work in [11], in terms of view serializability, and later re-formulated by Adya [9] in terms of conflict serializability. We report in the following the latter specification of this consistency criterion.…”
Section: System and Data Modelmentioning
confidence: 99%
“…In terms of formal properties, our protocol (as its name suggests) ensures the so called Extended Update Serializability (EUS) consistency criterion, originally introduced in [11] and further investigated in [9] (in the form of the noupdate-conflict-misses property). EUS provides guarantees analogous to those offered by classic 1-Copy Serializability (1CS) for update transactions, thus ensuring consistent evolution of the system's state.…”
Section: Introductionmentioning
confidence: 99%