The virtues of locking by symbolic names
Journal of Algorithms
Leases: an efficient fault-tolerant mechanism for distributed file cache consistency
SOSP '89 Proceedings of the twelfth ACM symposium on Operating systems principles
Transaction chopping: algorithms and performance studies
ACM Transactions on Database Systems (TODS)
A critique of ANSI SQL isolation levels
SIGMOD '95 Proceedings of the 1995 ACM SIGMOD international conference on Management of data
Generalized Isolation Level Definitions
ICDE '00 Proceedings of the 16th International Conference on Data Engineering
Semantic Conditions for Correctness at Different Isolation Levels
ICDE '00 Proceedings of the 16th International Conference on Data Engineering
A read-only transaction anomaly under snapshot isolation
ACM SIGMOD Record
Ganymed: scalable replication for transactional web applications
Proceedings of the 5th ACM/IFIP/USENIX international conference on Middleware
Postgres-R(SI): Combining Replica Control with Concurrency Control Based on Snapshot Isolation
ICDE '05 Proceedings of the 21st International Conference on Data Engineering
Allocating isolation levels to transactions
Proceedings of the twenty-fourth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Middleware based data replication providing snapshot isolation
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Making snapshot isolation serializable
ACM Transactions on Database Systems (TODS)
Database Replication Using Generalized Snapshot Isolation
SRDS '05 Proceedings of the 24th IEEE Symposium on Reliable Distributed Systems
Lazy database replication with snapshot isolation
VLDB '06 Proceedings of the 32nd international conference on Very large data bases
Boxwood: abstractions as the foundation for storage infrastructure
OSDI'04 Proceedings of the 6th conference on Symposium on Opearting Systems Design & Implementation - Volume 6
The Chubby lock service for loosely-coupled distributed systems
OSDI '06 Proceedings of the 7th symposium on Operating systems design and implementation
Automating the detection of snapshot isolation anomalies
VLDB '07 Proceedings of the 33rd international conference on Very large data bases
Serializable isolation for snapshot databases
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
The Cost of Serializability on Platforms That Use Snapshot Isolation
ICDE '08 Proceedings of the 2008 IEEE 24th International Conference on Data Engineering
A Robust Technique to Ensure Serializable Executions with Snapshot Isolation DBMS
ICDE '09 Proceedings of the 2009 IEEE International Conference on Data Engineering
Serializable isolation for snapshot databases
ACM Transactions on Database Systems (TODS)
Quantifying isolation anomalies
Proceedings of the VLDB Endowment
DASFAA'08 Proceedings of the 13th international conference on Database systems for advanced applications
Precisely Serializable Snapshot Isolation (PSSI)
ICDE '11 Proceedings of the 2011 IEEE 27th International Conference on Data Engineering
Real-time quantification and classification of consistency anomalies in multi-tier architectures
ICDE '11 Proceedings of the 2011 IEEE 27th International Conference on Data Engineering
One-copy serializability with snapshot isolation under the hood
ICDE '11 Proceedings of the 2011 IEEE 27th International Conference on Data Engineering
Multi-version Concurrency via Timestamp Range Conflict Management
ICDE '12 Proceedings of the 2012 IEEE 28th International Conference on Data Engineering
Serializable snapshot isolation in PostgreSQL
Proceedings of the VLDB Endowment
| Hi-index | 0.00 |
Snapshot Isolation (SI) is a multiversion concurrency control that has been implemented by several open source and commercial database systems (Oracle, Microsoft SQL Server, and previous releases of PostgreSQL). The main feature of SI is that a read operation does not block a write operation and vice versa, which allows higher degree of concurrency than traditional two-phase locking. SI prevents many anomalies that appear in other isolation levels, but it still can result in non-serializable executions, in which database integrity constraints can be violated. Several techniques are known to modify the application code based on preanalysis, in order to ensure that every execution is serializable on engines running SI. We introduce a new technique called External Lock Manager (ELM). In using a technique, there is a choice to make, of which pairs of transactions need to have conflicts introduced. We measure the performance impact of the choices available, among techniques and conflicts.