Timestamping after commit

Author

Salzberg, Betty

Author_Institution

Coll. of Comput. Sci., Northeastern Univ., Boston, MA, USA

fYear

1994

fDate

28-30 Sep 1994

Firstpage

160

Lastpage

167

Abstract

Many applications need transaction-consistent pictures of past states of the database. These applications use the commit time of the transaction to timestamp the data. When a transaction is distributed, the cohorts must vote on a commit time and the coordinator must choose a commit time based on the votes of the cohorts. This implies that timestamps are applied after commit. Until the timestamps are on all the records, one must keep a table of all the committed transaction identifiers and their commit times. The main problem solved is that of determining when all timestamps corresponding to a given transaction have been placed in the records so that a committed transaction entry can be erased from the table. This information must be stable. Logging and recovery details are included

Keywords

concurrency control; data recording; distributed databases; system recovery; transaction processing; cohort voting; committed transaction identifiers; coordinator; distributed transactions; logging; past database states; recovery; stable information; table entry deletion; timestamping; transaction commit time; Application software; Computer science; Concurrency control; Concurrent computing; Data analysis; Educational institutions; Relational databases; Stock markets; Transaction databases; Voting;

fLanguage

English

Publisher

ieee

Conference_Titel

Parallel and Distributed Information Systems, 1994., Proceedings of the Third International Conference on

Conference_Location

Austin, TX

Print_ISBN

0-8186-6400-2

Type

conf

DOI

10.1109/PDIS.1994.331720

Filename

331720