RE: WAL & SHM principles

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Kevin T(dot) Manley (Home)'" <kmanley(at)uswest(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: RE: WAL & SHM principles
Date: 2001-03-13 00:25:17
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3312@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> > It is possible to build a logging system so that you
>> > mostly don't care when the data blocks get written;
>> > a particular data block on disk is considered garbage
>> > until the next checkpoint, so that you
>> >
> > How to know if a particular data page was modified if there is no
> > log record for that modification?
> > (Ie how to know where is garbage? -:))
>
> You could store a log sequence number in the data page header
> that indicates the log address of the last log record that was
> applied to the page.

We do. But how to know at the time of recovery that there is
a page in multi-Gb index file with tuple pointing to uninserted
table row?
Well, actually we could make some improvements in this area:
a buffer without "first after checkpoint" modification could be
written without flushing log records: entire block will be
rewritten on recovery. Not sure how much we get, though -:)

Vadim

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-03-13 00:27:50 RE: xlog patches reviewed
Previous Message The Hermit Hacker 2001-03-13 00:24:37 Re: xlog patches reviewed