| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |
| Date: | 2012-10-08 14:08:00 |
| Message-ID: | CA+TgmoYQotjpMU2J6L9ODVnC6-AmqsHd2mUnNW332CpV77sZxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, Oct 4, 2012 at 6:12 AM, Amit kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> 1. One new configuration parameter wal_receiver_timeout is added to detect timeout at receiver task.
> 2. Existing parameter replication_timeout is renamed to wal_sender_timeout.
-1 from me on a backward compatibility break here. I don't know what
else to call the new GUC (replication_server_timeout?) but I'm not
excited about breaking existing conf files, nor do I particularly like
the proposed new names.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-10-08 14:42:23 | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |
| Previous Message | Nikolay | 2012-10-08 11:45:20 | Re: BUG #7578: Not able to drop user if S/he has permission on tablespace |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-10-08 14:18:04 | Re: Missing OID define |
| Previous Message | Peter Geoghegan | 2012-10-08 14:03:03 | Re: enhanced error fields |