| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Amit kapila <amit(dot)kapila(at)huawei(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-02 00:02:54 |
| Message-ID: | CA+TgmoZxXymQDQ=s7dF_dU9+3hU-iDeCQpGmUQ-GrQYEQ1TQ3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Oct 1, 2012 at 12:57 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> I believe many users are basically familiar with TCP keepalives and how to
> specify it. So I think that this approach would be intuitive to users.
My experience is that many users are unfamiliar with TCP keepalives
and that when given the options they tend to do it wrong. I think a
simpler system would be better.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-10-02 03:50:42 | Re: BUG #7534: walreceiver takes long time to detect n/w breakdown |
| Previous Message | Freddie Burgess | 2012-10-01 20:18:42 | Postgres 9.2 with Postgis 1.5.3 Upgrade |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-10-02 00:57:18 | small LDAP error message change |
| Previous Message | Hitoshi Harada | 2012-10-01 22:34:17 | Re: date_in and buffer overrun |