Re: Cascaded standby message

From: Thom Brown <thom(at)linux(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cascaded standby message
Date: 2011-09-07 12:10:25
Message-ID: CAA-aLv5FjSFCuRAPf4fMa_vp5giE4shSQ7FiNNfRUwJF1kOe8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7 September 2011 11:56, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> 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.
> <http://www.postgresql.org/mailpref/pgsql-hackers>
>

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2011-09-07 12:37:52 Re: Cascaded standby message
Previous Message Simon Riggs 2011-09-07 11:15:50 Re: savepoint commit performance