Jump to content

Talk:Algorithms for Recovery and Isolation Exploiting Semantics

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 80.56.194.175 (talk) at 08:54, 14 February 2016. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Start‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StartThis article has been rated as Start-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

Redo

Why does the ARIES redo all tansactions and not only the commited ones? 212.25.82.123 (talk) 11:10, 1 November 2010 (UTC)[reply]

See What is the benefit of repeating history in ARIES recovery method? Franck Dernoncourt (talk) 03:24, 9 April 2013 (UTC)[reply]

Redo

The article claims the following:

If page P exists in the DPT table, then we see whether the Sequence Number in the DPT is smaller than the Sequence Number of the log record (i.e. whether the change in the log is newer than the last version that was persisted). If it isn't, then we don't redo the entry since the change is already there. If it is, we fetch the page from the database storage and check the Sequence Number stored on the page to the Sequence Number on the log record. If the former is smaller than the latter, the page does not need to be written to the disk.

The last sentence seems wrong to me. Shouldn't this be the other way around? In case the Sequence Number stored on the page is older than the Sequence Number on the log the page needs to be written to disk. Mohlerm (talk) 08:43, 9 August 2015 (UTC)[reply]

The article claims the following:

Every time a transaction begins or commits we write a "Begin Transaction" entry or an "End Of Log" entry for that transaction respectively.

But in the original paper there's nothing like explicit "Begin Transaction" except for 2PC transactions, which is "Prepare" record.