Using the Lock Manager to Choose Timestamps

D. Lomet, R.T. Snodgrass, Christian Søndergaard Jensen

Research output: Contribution to book/anthology/report/conference proceedingArticle in proceedingResearchpeer-review

3 Citations (Scopus)

Abstract

Our goal is to support transaction-time functionality that enables the coexistence of ordinary, non-temporal tables with transaction-time tables. In such a system, each transaction updating a transaction-time or snapshot table must include a timestamp for its updated data that correctly reflects the serialization order of the transactions, including transactions on ordinary tables. A serious issue is coping with SQL CURRENT_TIME functions, which should return a time consistent with a transaction's timestamp and serialization order. Prior timestamping techniques cannot support such functions with this desired semantics. We show how to compatibly extend conventional database functionality for transactiontime support by exploiting the database system lock manager and by utilizing a spectrum of optimizations.
Original languageEnglish
Title of host publicationProceedings of the Nineth International Database Engineering and Applications Symposium
Publication date2005
Pages357-368
Publication statusPublished - 2005
EventInternational Database Engineering and Applications Symposium - Montreal, Canada
Duration: 25 Jul 200527 Jul 2005
Conference number: 9

Conference

ConferenceInternational Database Engineering and Applications Symposium
Number9
CountryCanada
CityMontreal
Period25/07/200527/07/2005

Fingerprint Dive into the research topics of 'Using the Lock Manager to Choose Timestamps'. Together they form a unique fingerprint.

Cite this