From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Tatsuo Ishii'" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | RE: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
Date: | 2000-11-16 21:31:54 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A234D318A@sectorbase1.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > > 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
From | Date | Subject | |
---|---|---|---|
Next Message | Alfred Perlstein | 2000-11-16 21:36:30 | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
Previous Message | Tom Lane | 2000-11-16 21:31:37 | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |