BUG #7534: walreceiver takes long time to detect n/w breakdown - Mailing list pgsql-bugs

From amit.kapila@huawei.com
Subject BUG #7534: walreceiver takes long time to detect n/w breakdown
Date
Msg-id E1TBlX1-0003OA-SB@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #7534: walreceiver takes long time to detect n/w breakdown  (Magnus Hagander <magnus@hagander.net>)
Re: BUG #7534: walreceiver takes long time to detect n/w breakdown  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      7534
Logged by:          Amit Kapila
Email address:      amit.kapila@huawei.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. =

pgsql-bugs by date:

Previous
From: amit.kapila@huawei.com
Date:
Subject: BUG #7533: Client is not able to connect cascade standby incase basebackup is taken from hot standby
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations