| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Spreading full-page writes |
| Date: | 2014-05-26 17:16:33 |
| Message-ID: | 81D16E69-BA9C-45FF-97B7-DFF756C489B8@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 25, 2014, at 5:52 PM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)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.)
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-05-26 17:22:38 | Re: Spreading full-page writes |
| Previous Message | Tom Lane | 2014-05-26 16:39:01 | Re: Re: popen and pclose redefinitions causing many warning in Windows build |