Using the lock manager to choose timestamps

David Lomet, Richard T. Snodgrass, Christian S. Jensen

Research output: Contribution to journalConference article

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)
Article number1540926
Pages (from-to)357-368
Number of pages12
JournalProceedings of the International Database Engineering and Applications Symposium, IDEAS
Volume2005-January
Issue numberJanuary
DOIs
StatePublished - Jan 1 2005
Event9th International Database Engineering and Application Symposium, IDEAS 2005 - Montreal, Canada
Duration: Jul 25 2005Jul 27 2005

ASJC Scopus subject areas

  • Computer Science(all)
  • Engineering(all)

Fingerprint Dive into the research topics of 'Using the lock manager to choose timestamps'. Together they form a unique fingerprint.

  • Cite this