Abstraction in recovery management
- 15 June 1986
- journal article
- Published by Association for Computing Machinery (ACM) in ACM SIGMOD Record
- Vol. 15 (2) , 72-83
- https://doi.org/10.1145/16856.16862
Abstract
There are many examples of actions on abstract data types which can be correctly implemented with nonserializable and nonrecoverable schedules of reads and writes. We examine a model of multiple layers of abstraction that explains this phenomenon and suggests an approach to building layered systems with transaction oriented synchronization and roll back. Our model may make it easier to provide the high data integrity of reliable database transaction processing in a broader class of information systems. We concentrate on the recovery aspects here, a technical report [Moss et al 85] has a more complete discussion of concurrency control.Keywords
This publication has 8 references indexed in Scilit:
- Synchronizing shared abstract typesACM Transactions on Computer Systems, 1984
- Principles of transaction-oriented database recoveryACM Computing Surveys, 1983
- Multilevel atomicity—a new correctness criterion for database concurrency controlACM Transactions on Database Systems, 1983
- A concurrency control theory for nested transactions (Preliminary Report)Published by Association for Computing Machinery (ACM) ,1983
- An operational model for database system reliabilityPublished by Association for Computing Machinery (ACM) ,1983
- Read-only transactions in a distributed databaseACM Transactions on Database Systems, 1982
- The serializability of concurrent database updatesJournal of the ACM, 1979
- The notions of consistency and predicate locks in a database systemCommunications of the ACM, 1976