Using the lock manager to choose timestamps

David Lomet, Richard Thomas Snodgrass, Christian S. Jensen

Research output: Chapter in Book/Report/Conference proceedingConference contribution

3 Scopus citations

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 junctions with this desired semantics. We show how to compatibly extend conventional database functionality for transaction-time support by exploiting the database system lock manager and by utilizing a spectrum of optimizations.

Original languageEnglish (US)
Title of host publicationProceedings of the International Database Engineering and Applications Symposium, IDEAS
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages357-368
Number of pages12
Volume2005-January
EditionJanuary
DOIs
Publication statusPublished - 2005
Event9th International Database Engineering and Application Symposium, IDEAS 2005 - Montreal, Canada
Duration: Jul 25 2005Jul 27 2005

Other

Other9th International Database Engineering and Application Symposium, IDEAS 2005
CountryCanada
CityMontreal
Period7/25/057/27/05

    Fingerprint

ASJC Scopus subject areas

  • Computer Science(all)

Cite this

Lomet, D., Snodgrass, R. T., & Jensen, C. S. (2005). Using the lock manager to choose timestamps. In Proceedings of the International Database Engineering and Applications Symposium, IDEAS (January ed., Vol. 2005-January, pp. 357-368). [1540926] Institute of Electrical and Electronics Engineers Inc.. https://doi.org/10.1109/IDEAS.2005.53