| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Toru SHIMOGAKI <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: proposal: setKeepAlive |
| Date: | 2008-02-08 17:43:19 |
| Message-ID: | Pine.BSO.4.64.0802081233060.19198@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 8 Feb 2008, Gregory Stark wrote:
> "Toru SHIMOGAKI" <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp> writes:
>
>> The attached makes tcp-keep-alive enable. When PostgreSQL server gets down or
>> network gets down, client application can't receive any response from the server.
>
> This has to be an option, not on unconditionally. In fact they shouldn't
> be on automatically. Applications should have to explicitly request TCP
> keep-alives and set an application-specific appropriate interval.
> Otherwise you're breaking TCP in general for a behaviour which is only
> useful in particular circumstances.
Java does not support a configurable keepalive interval, it's simply an
on/off flag.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-02-08 21:26:49 | Re: proposal: setKeepAlive |
| Previous Message | Gregory Stark | 2008-02-08 17:25:03 | Re: proposal: setKeepAlive |