ACM Home Page
Please provide us with feedback. Feedback
A read-only transaction anomaly under snapshot isolation
Full text PdfPdf (86 KB)
Source ACM SIGMOD Record archive
Volume 33 ,  Issue 3  (September 2004) table of contents
COLUMN: Articles table of contents
Pages: 12 - 14  
Year of Publication: 2004
ISSN:0163-5808
Authors
Alan Fekete  NSF Grant IRI
Elizabeth O'Neil  NSF Grant IRI
Patrick O'Neil  NSF Grant IRI
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 67,   Citation Count: 5
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1031570.1031573
What is a DOI?

ABSTRACT

Snapshot Isolation (SI), is a multi-version concurrency control algorithm introduced in [BBGMOO95] and later implemented by Oracle. SI avoids many concurrency errors, and it never delays read-only transactions. However it does not guarantee serializability. It has been widely assumed that, under SI, read-only transactions always execute serializably provided the concurrent update transactions are serializable. The reason for this is that all SI reads return values from a single instant of time when all committed transactions have completed their writes and no writes of non-committed transactions are visible. This seems to imply that read-only transactions will not read anomalous results so long as the update transactions with which they execute do not write such results. In the current note, however, we exhibit an example contradicting these assumptions: it is possible for an SI history to be non-serializable while the sub-history containing all update transactions is serializable.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
 
4
{F99} A. Fekete. Serializability and Snapshot Isolation. Proceedings of the Australian Database Conference, Auckland, New Zealand, January 1999. Pages 201--210.
 
5
 
6
{JAC95} K. Jacobs, with contributors: R. Bamford, G. Doherty, K. Haas, M. Holt, F. Putzolu, B. Quigley. Concurrency Control: Transaction Isolation and Serializability in SQL92 and Oracle7. Oracle White Paper, Part No. A33745, July, 1995.
 
7
 
8
{TPC-C} TPC-C Benchmark Specification, available at <u>http://www.tpc.org/</u>

Collaborative Colleagues:
Alan Fekete: colleagues
Elizabeth O'Neil: colleagues
Patrick O'Neil: colleagues