Skip site navigation (1) Skip section navigation (2)

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

From: amit(dot)kapila(at)huawei(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7534: walreceiver takes long time to detect n/w breakdown
Date: 2012-09-12 11:54:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
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

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, 

master can detect connect abnormal, but the standby can't detect connect
abnormal and show a connected channel long time. 


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2012-09-12 12:00:31
Subject: Re: Doc typo: lexems -> lexemes
Previous:From: Amit KapilaDate: 2012-09-12 11:35:30
Subject: Re: Issue observed in cascade standby setup and analysis for same

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2012-09-12 13:05:39
Subject: Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations
Previous:From: amit.kapilaDate: 2012-09-12 11:47:16
Subject: BUG #7533: Client is not able to connect cascade standby incasebasebackup is taken from hot standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group