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

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

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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


In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2012-10-02 00:57:18
Subject: small LDAP error message change
Previous:From: Hitoshi HaradaDate: 2012-10-01 22:34:17
Subject: Re: date_in and buffer overrun

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2012-10-02 03:50:42
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous:From: Freddie BurgessDate: 2012-10-01 20:18:42
Subject: Postgres 9.2 with Postgis 1.5.3 Upgrade

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