Re: why do you apply undo before redo?

From: Dan <>
Date: Tue, 20 Apr 2004 10:00:28 GMT
Message-ID: <0x6hc.24485$>

"Wayne Warren" <> wrote in message news:WWTgc.85993$
> I'm not sure that the book is correct. I wrote a transaction processing
> system (released on 1993 as Velocis Database Server, now called Birdstep
> Server) which performs redo operations just prior to undo operations. I
> assure you that in practice it works.
> If transactions have maintained proper Isolation (the "I" in ACID) from
> another, then the order of redo/undo should be irrelevant.

But we still have to worry about getting the database to a consistent state, regardless of active interleaving at time of failure. The use of caches means that some commited transactions might not have been written to disk, or in other cases, parts of uncompleted transactions did get written to disk and need to be undone. Though there might be interleaving across transactions at the time of failure, the DBMS doesn't need to consider some of these transactions if they were propery persisted. Thus some serializable schedule might no longer apply.

  • Dan

> specifics may dictate the order, but the transaction recovery concept does
> not.
> "Ryan" <> wrote in message
> news:_Ulgc.4499$uF3.1441_at_lakeread04...
> > I'm reading a generic database textbook and it states that when
> > are recovering undo is applied before redo. It doesn't say why. Does
> anyone
> > know?
> >
> >
Received on Tue Apr 20 2004 - 12:00:28 CEST

Original text of this message