Data Mgmt Lab_Part_61 - Crash Recovery 181 10 20 30 40 50...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Crash Recovery 181 10 20 30 40 50 60 00 end_checkpoint begin_checkpoint LOG LSN update: T1 writes P5 update: T2 writes P3 update: T3 writes P3 CRASH, RESTART T2 end T2 commit T1 abort 70 Figure 18.1 Execution with a Crash (b) The dirty pages in the buffer pool at the time of the crash. (c) Transactions that were active at the time of the crash which need to be undone. The Redo phase follows Analysis and redoes all changes to any page that might have been dirty at the time of the crash. The Undo phase follows Redo and undoes the changes of all transactions that were active at the time of the crash. 2. (a) For this example, we will assume that the Dirty Page Table and Transaction Table were empty before the start of the log. Analysis determines that the last begin checkpoint was at LSN 00 and starts at the corresponding end checkpoint (LSN 10). We will denote Transaction Table records as (transID, lastLSN) and Dirty Page Table records as (pageID, recLSN) sets....
View Full Document

Page1 / 3

Data Mgmt Lab_Part_61 - Crash Recovery 181 10 20 30 40 50...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online