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

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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Amit kapila <amit(dot)kapila(at)huawei(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Date: 2012-10-02 03:50:42
Message-ID: 1349149814-sup-7217@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Excerpts from Robert Haas's message of lun oct 01 21:02:54 -0300 2012:
> 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.

+1

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2012-10-02 06:37:16
Subject: Re: Installation of xpath (read xml on postgres)
Previous:From: sccDate: 2012-10-02 03:08:36
Subject: Re: moving system catalogs to another tablespace

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2012-10-02 03:59:10
Subject: Re: BUG #7574: CASE in WHERE condition change result set
Previous:From: Robert HaasDate: 2012-10-02 00:02:54
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

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