From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Cascaded standby message |
Date: | 2011-09-07 10:56:15 |
Message-ID: | CA+U5nM+-v2zsYj+9r=1xNjomZXj6a=x2yx_RgfAo42zQH=9bnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 7, 2011 at 2:44 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Sep 7, 2011 at 5:22 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Fujii - the original goal here was to avoid having a unexplained
>> disconnection in the logs. The only way to do this cleanly is to have
>> a disconnection reason passed to the walsender, rather than just a
>> blind signal. Looks like we need to multiplex or other mechanism.
>
> That's an idea. But what about the patch that I proposed before?
> http://archives.postgresql.org/pgsql-hackers/2011-08/msg00816.php
Thanks for that. Committed.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-09-07 11:15:50 | Re: savepoint commit performance |
Previous Message | Magnus Hagander | 2011-09-07 10:47:56 | Re: Cascaded standby message |