Re: Cascaded standby message - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Cascaded standby message
Date
Msg-id CAA-aLv5FjSFCuRAPf4fMa_vp5giE4shSQ7FiNNfRUwJF1kOe8Q@mail.gmail.com
Whole thread Raw
In response to Re: Cascaded standby message  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Cascaded standby message
List pgsql-hackers
On 7 September 2011 11:56, Simon Riggs <simon@2ndquadrant.com> wrote:
On Wed, Sep 7, 2011 at 2:44 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Wed, Sep 7, 2011 at 5:22 AM, Simon Riggs <simon@2ndquadrant.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.

This appears to be the patch submitted to the commitfest.  https://commitfest.postgresql.org/action/patch_view?id=630  Can this now be marked as committed?

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: savepoint commit performance
Next
From: Fujii Masao
Date:
Subject: Re: Cascaded standby message