Re: RE: [COMMITTERS] pgsql/src/backend/access/transam (xact.c xlog.c) - Mailing list pgsql-hackers

From devik@cdi.cz
Subject Re: RE: [COMMITTERS] pgsql/src/backend/access/transam (xact.c xlog.c)
Date
Msg-id 3A18165E.ABB18155@cdi.cz
Whole thread Raw
In response to RE: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
Responses Re: RE: [COMMITTERS] pgsql/src/backend/access/transam (xact.c xlog.c)  (Don Baccus <dhogaza@pacifier.com>)
List pgsql-hackers
"Mikheev, Vadim" wrote:
> 
> > > > > No. Checkpoints are to speedup after crash recovery and
> > > > > to remove/archive log files. With WAL server doesn't write
> > > > > any datafiles on commit, only commit record goes to log
> > > > > (and log fsync-ed). Dirty buffers remains in memory long
> >
> > Ok, so with CHECKPOINTS, we could move the offline log files to
> > somewhere else so that we could archive them, in my
> > undertstanding. Now question is, how we could recover from disaster
> > like losing every table files except log files. Can we do this with
> > WAL? If so, how can we do it?
> 
> Not currently. WAL based BAR is required. I think there will be no BAR
> in 7.1, but it may be added in 7.1.X (no initdb will be required).
> Anyway BAR implementation is not in my plans. All in your hands, guys -:)
> 
> Vadim

Cam I ask what BAR is ?



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WAL fsync scheduling
Next
From: "Vadim Mikheev"
Date:
Subject: Re: WAL fsync scheduling