Re: Cascaded standby message - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Cascaded standby message
Date
Msg-id CABUevEzhkFhRjWu_pxoX_jrGU-uro_Znw65k6WL3y-NG3E8LpA@mail.gmail.com
Whole thread Raw
In response to Re: Cascaded standby message  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Sep 7, 2011 at 03:44, 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

Seems like a good solution to me - I hadn't noticed that patch before
posting my complaint.

I don't think it's a problem if it logs it multiple times when it
happens - I think it's a much bigger problem that it logs it when it
didn't actually do anything.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: daveg
Date:
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held
Next
From: Simon Riggs
Date:
Subject: Re: Cascaded standby message