| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WALWriter active during recovery |
| Date: | 2014-12-16 17:07:48 |
| Message-ID: | CA+U5nMLpKinwDqVHbkED1tdut+Cg_6bLn8YSsre1Zid3rGtWag@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 December 2014 at 14:12, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> On 12/15/2014 08:51 PM, Simon Riggs wrote:
>>
>> Currently, WALReceiver writes and fsyncs data it receives. Clearly,
>> while we are waiting for an fsync we aren't doing any other useful
>> work.
>>
>> Following patch starts WALWriter during recovery and makes it
>> responsible for fsyncing data, allowing WALReceiver to progress other
>> useful actions.
>
>
> What other useful actions can WAL receiver do while it's waiting? It doesn't
> do much else than receive WAL, and fsync it to disk.
So now it will only need to do one of those two things.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-12-16 17:07:59 | Re: 9.5 release scheduling (was Re: logical column ordering) |
| Previous Message | Teodor Sigaev | 2014-12-16 17:07:38 | Re: speedup tidbitmap patch: hash BlockNumber |