| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: Spreading full-page writes |
| Date: | 2014-05-28 06:41:06 |
| Message-ID: | CA+U5nM+Gm824JQuxQsVJ81F4EOr=VhFOAyGLUt47MYuKrPSnEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27 May 2014 13:20, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> On 05/27/2014 03:18 PM, Simon Riggs wrote:
>>
>> IIRC Koichi had a patch for prefetch during recovery. Heikki, is that
>> the reason you also discussed changing the WAL record format to allow
>> us to identify the blocks touched by recovery more easily?
>
>
> Yeah, that was one use case I had in mind for the WAL format changes. See
> http://www.postgresql.org/message-id/533D6CBF.6080203@vmware.com.
Those proposals suggest some very big changes to the way WAL works.
Prefetch can work easily enough for most records - do we really need
that much churn?
You mentioned Btree vacuum records, but I'm planning to optimize those
another way.
Why don't we just have the prefetch code in core and forget the WAL
format changes?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-05-28 06:47:33 | Re: Spreading full-page writes |
| Previous Message | Andrew Dunstan | 2014-05-28 06:35:16 | Re: json casts |