Re: support for keep alive option

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>
Cc: Barry Bell <Barry(dot)Bell(at)hartehanks(dot)com>, PG User <pguser1982(at)gmail(dot)com>, Hiroshi Saito <hiroshi(at)winpg(dot)jp>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>, Pavel Raiskup <praiskup(at)redhat(dot)com>
Subject: Re: support for keep alive option
Date: 2014-01-08 09:20:46
Message-ID: 52CD186E.3040504@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 01/08/2014 01:48 AM, Inoue, Hiroshi wrote:
> Hi Barry,
>
> Sorry for the late reply.
>
> (2014/01/02 23:02), Barry Bell wrote:
>> Thanks, Alright with me to add the patch in
>>
>> But you may want to Hiroshi (He does the office and unofficial ODBC
>> driver releases),
>>
>> Hiroshi, what do you think of this?
>
> OK I would introduce the functionality.

I don't think it should be enabled by default. It's common to expose
keepalive and other TCP settings as an option, like libpq does, but it's
not usually enabled by default, and it might be an unwelcome surprise to
some existing applications.

In particular, if you have a dialup connection, you do *not* want an
idle connection to keep sending periodic keep-alives, because keeping
the connection open costs money. It's not as big a problem these days as
it used to be, but still.

- Heikki

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2014-01-08 11:40:29 Re: support for keep alive option
Previous Message Inoue, Hiroshi 2014-01-07 23:48:22 Re: support for keep alive option