Using the Lock Manager to Choose Timestamps

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

Publikation: Bidrag til bog/antologi/rapport/konference proceedingKonferenceartikel i proceedingForskningpeer review

3 Citationer (Scopus)

Abstrakt

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.
OriginalsprogEngelsk
TitelProceedings of the Nineth International Database Engineering and Applications Symposium
Publikationsdato2005
Sider357-368
StatusUdgivet - 2005
BegivenhedInternational Database Engineering and Applications Symposium - Montreal, Canada
Varighed: 25 jul. 200527 jul. 2005
Konferencens nummer: 9

Konference

KonferenceInternational Database Engineering and Applications Symposium
Nummer9
LandCanada
ByMontreal
Periode25/07/200527/07/2005

Fingeraftryk

Dyk ned i forskningsemnerne om 'Using the Lock Manager to Choose Timestamps'. Sammen danner de et unikt fingeraftryk.

Citationsformater