| 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: | E1TBlX1-0003OA-SB@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-09-12 13:05:39 | Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations |
| Previous Message | amit.kapila | 2012-09-12 11:47:16 | BUG #7533: Client is not able to connect cascade standby incase basebackup is taken from hot standby |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-09-12 12:00:31 | Re: Doc typo: lexems -> lexemes |
| Previous Message | Amit Kapila | 2012-09-12 11:35:30 | Re: Issue observed in cascade standby setup and analysis for same |