Integrated concurrency control and recovery mechanisms: design and performance evaluation
ACM Transactions on Database Systems (TODS)
The theory of database concurrency control
The theory of database concurrency control
On Concurrency Control by Multiple Versions
ACM Transactions on Database Systems (TODS)
Models for studying concurrency control performance: alternatives and implications
SIGMOD '85 Proceedings of the 1985 ACM SIGMOD international conference on Management of data
On optimistic methods for concurrency control
ACM Transactions on Database Systems (TODS)
Concurrency control in a system for distributed databases (SDD-1)
ACM Transactions on Database Systems (TODS)
The serializability of concurrent database updates
Journal of the ACM (JACM)
A Theory of Safe Locking Policies in Database Systems
Journal of the ACM (JACM)
The notions of consistency and predicate locks in a database system
Communications of the ACM
An optimality theory of concurrency control for databases
SIGMOD '79 Proceedings of the 1979 ACM SIGMOD international conference on Management of data
Proceedings of the Fourth International Conference on Data Engineering
Concurrency Control by Pre-Ordering Entities in Databases with Multi-Versioned Entities
Proceedings of the Third International Conference on Data Engineering
Implementing atomic actions on decentralized data (Extended Abstract)
SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles
NAMING AND SYNCHRONIZATION IN A DECENTRALIZED COMPUTER SYSTEM
NAMING AND SYNCHRONIZATION IN A DECENTRALIZED COMPUTER SYSTEM
Consistency and concurrency in distributed databases: development and evaluation of protocols (pre-ordering, transaction-state)
Hi-index | 0.00 |
In this paper, we present a concurrency control protocol for databases with universioned entities; the database could be either centralized or distributed and may or may not have data replication. In this protocol, entities are assigned an order and whenever possible each transaction accesses entities in this order, entities that need not be accessed by a transaction may be skipped by the transaction, and out-of-order accesses are permitted at an additional cost. Also, each transaction carries with it, as it moves along the preordered entities, the state information about all preceding transactions which must execute logically before this transaction at all succeeding entities to ensure serializability of schedules. At each entity, a transaction executes logically after all the transactions in the state carried to the entity by the transaction.