Re: beta3 & the open items list

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <fgp(at)phlo(dot)org>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <robertmhaas(at)gmail(dot)com>,<gsstark(at)mit(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: beta3 & the open items list
Date: 2010-06-20 13:54:00
Message-ID: 4C1DD7280200002500032618@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Pflug wrote:
> On Jun 20, 2010, at 7:18 , Tom Lane wrote:

>> I was thinking that keepalive was on by default with a very
>> long interval, but I see this isn't so. However, if we enable
>> keepalive, then it's irrelevant to the point anyway. Nobody's
>> produced any evidence that keepalive is an unsuitable solution.
>
> Yeah, I agree. Just enabling keepalive should suffice for 9.0.

+1, with configurable timeout; otherwise people will often feel they
need to kill the receiver process to get it to attempt reconnect or
archive search, anyway. Two hours is a long time to block
replication based on a broken connection before attempting to move
on.

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2010-06-20 15:02:37 Re: extensible enum types
Previous Message Simon Riggs 2010-06-20 10:56:30 Small FSM is too large