Re: Spreading full-page writes - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Spreading full-page writes
Date
Msg-id 32349dda-e62c-4a13-940c-1268bbca823e@email.android.com
Whole thread Raw
In response to Re: Spreading full-page writes  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Spreading full-page writes  (Greg Stark <stark@mit.edu>)
Re: Spreading full-page writes  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 26 May 2014 20:16:33 EEST, Robert Haas <robertmhaas@gmail.com> wrote:
>On May 25, 2014, at 5:52 PM, Heikki Linnakangas
><hlinnakangas@vmware.com> wrote:
>> Here's how this works out during replay:
>> 
>> a) You start WAL replay from the latest checkpoint's Redo-pointer.
>> 
>> When you see a WAL record that's been marked with XLR_FPW_SKIPPED,
>don't replay that record at all. It's OK because we know that there
>will be a separate record containing the full-page image of the page
>later in the stream.
>
>I don't think we know that. The server might have crashed before that
>second record got generated.  (This appears to be an unfixable flaw in
>this proposal.)

The second record is generated before the checkpoint is finished and the checkpoint record is written.  So it will be
there.

(if you crash before the checkpoint is finished, the in-progress checkpoint is no good for recovery anyway, and won't
beused)
 

- Heikki



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Spreading full-page writes
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Replacement for OSSP-UUID for Linux and BSD