RE: WAL & SHM principles - Mailing list pgsql-hackers

From Martin Devera
Subject RE: WAL & SHM principles
Date
Msg-id Pine.LNX.4.10.10103091555420.12401-100000@luxik.cdi.cz
Whole thread Raw
In response to RE: WAL & SHM principles  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
> > Pros: upper layers can think thet buffers are always safe/logged and
> >       there is no special handling for indices; very simple/fast redo
> > Cons: can't implement undo - but in non-overwriting is not needed (?)
> 
> But needed if we want to get rid of vacuum and have savepoints.

Hmm. How do you implement savepoints ? When there is rollback to savepoint
do you use xlog to undo all changes which the particular transaction has
done ? Hmmm it seems nice ... these resords are locked by such transaction
so that it can safely undo them :-)
Am I right ?

But how can you use xlog to get rid of vacuum ? Do you treat all delete
log records as candidates for free space ?

regards, devik



pgsql-hackers by date:

Previous
From: Martin Devera
Date:
Subject: Re: WAL & SHM principles
Next
From: Tom Lane
Date:
Subject: Re: AW: WAL does not recover gracefully from out-of-disk-sp ace