Talk:Algorithms for Recovery and Isolation Exploiting Semantics
Latest comment: 1 year ago by Akira641z in topic Logging
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Redo edit
Why does the ARIES redo all tansactions and not only the commited ones? 212.25.82.123 (talk) 11:10, 1 November 2010 (UTC)
- See What is the benefit of repeating history in ARIES recovery method? Franck Dernoncourt (talk) 03:24, 9 April 2013 (UTC)
Redo edit
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)
- Nice catch! Apparently this was fixed by 2620:102:400b:1d12:d:b5aa:3f2a:184d in https://en.wikipedia.org/w/index.php?title=Algorithms_for_Recovery_and_Isolation_Exploiting_Semantics&diff=prev&oldid=716252077. Akira641z (talk) 09:59, 24 April 2023 (UTC)
Logging edit
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. — Preceding unsigned comment added by 80.56.194.175 (talk) 08:54, 14 February 2016 (UTC)