Sciweavers

Share
SIGMOD
2004
ACM

A Read-Only Transaction Anomaly Under Snapshot Isolation

12 years 1 days ago
A Read-Only Transaction Anomaly Under Snapshot Isolation
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.
Alan Fekete, Elizabeth J. O'Neil, Patrick E. O'Nei
Added 08 Dec 2009
Updated 08 Dec 2009
Type Conference
Year 2004
Where SIGMOD
Authors Alan Fekete, Elizabeth J. O'Neil, Patrick E. O'Neil
Comments (0)
books