Re: support for keep alive option
От | PG User |
---|---|
Тема | Re: support for keep alive option |
Дата | |
Msg-id | CAB7tN8aGxFpaaNZDPYFkMqT7=_84ovT_CroWhgOZ3Dn55mn52w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: support for keep alive option (PG User <pguser1982@gmail.com>) |
Ответы |
Re: support for keep alive option
|
Список | pgsql-odbc |
Do we know when the patch will be available in postgres odbc code for mentioned versions?
Thanking you.
- Nachiket
On Wed, Jan 8, 2014 at 11:12 AM, PG User <pguser1982@gmail.com> wrote:
Hi All,Thank you very much for your thoughts and discussions.I need a last favor:Is it possible for you to add functionality to postgres odbc version 9.x (latest) as well as 8.4.2?Thanking you.- NachiketOn Wed, Jan 8, 2014 at 4:06 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: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.I guess it would be best to enable it by default in psqlodbc as well, then.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.
- Heikki
В списке pgsql-odbc по дате отправления: