Using the Lock Manager to Choose Timestamps

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.

01540926.pdf
PDF file

In  IDEAS Conference

Publisher  IEEE Computer Society
Copyright © 2007 IEEE. Reprinted from IEEE Computer Society. This material is posted here with permission of the IEEE. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE by writing to pubs-permissions@ieee.org. By choosing to view this document, you agree to all provisions of the copyright laws protecting it.

Details

TypeInproceedings
> Publications > Using the Lock Manager to Choose Timestamps