| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Hiroshi Inoue <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 12:06:55 |
| Message-ID: | 52CD3F5F.7090309@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 01/08/2014 01:40 PM, Hiroshi Inoue wrote:
> (2014/01/08 18:20), Heikki Linnakangas wrote:
>> 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.
>
> Libpq's keepalives option is on by default.
Oh, I didn't realize that.
> So currently psqlodbc's
> keepalive is enabled when libpq is used(in case ssl used etc) otherwise
> it is disabled.
> Though I am about to enable keepalive by default, I'm not sure which
> should be the default.
I guess it would be best to enable it by default in psqlodbc as well, then.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Emery | 2014-01-08 12:59:17 | Fwd: Error installing ODBC Driver |
| Previous Message | Hiroshi Inoue | 2014-01-08 11:45:18 | Re: Error installing ODBC Driver |