Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

On Wed, Sep 12, 2012 at 1:54 PM, <amit(dot)kapila(at)huawei(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7534
> Logged by: Amit Kapila
> Email address: amit(dot)kapila(at)huawei(dot)com
> PostgreSQL version: 9.2.0
> Operating system: Suse 10
> Description:
>
> 1. Both master and standby machine are connected normally,
> 2. then you use the command: ifconfig ip down; make the network card of
> master and standby down,
>
> Observation
> master can detect connect abnormal, but the standby can't detect connect
> abnormal and show a connected channel long time.

The master will detect it quicker, because it will get an error when
it tries to send something.

But the standby should detect it either when sending the feedback
message (what's your wal_receiver_status_interval set to?) or when
ythe kernel does (have you configured the tcp keepalive on the slave
somehow?)

Oh, and what do you actually mean by "long time"?

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