>>> ISTM that the default behavior should be keep alives disabled, as it is
>>> now, and those wanting it can just set it in their apps:
>>> setsockopt(PQsocket(conn), SOL_SOCKET, SO_KEEPALIVE, ...)
>> I disagree. I have clients who have problems with leftover client connections
>> due to server host failures. They do not write apps in C. For a non-default
>> change to be effective we would need to have all the client drivers, eg JDBC,
>> psycopg, DBD-DBI, and the apps like psql make changes to turn it on. Adding
>> this option as a non-default will not really help.
> Yes, that's definitely the use-case. PQsocket() will work fine for C apps only.
> But it should work fine as an option, no? As long as you can specify
> it on the connection string - I don't think there are any interfaces
> that won't take a connection string?
Perl and python appear to have the same abilities as C. I don't use either of
these drivers but I *think* the below would work:
Although, I think Dave's comments have made me change my mind about this patch.
Looks like it serves a good purpose. That said, there is no guarentee the
driver will implement the new feature ... JDBC seems to lack the ability to get
the backing Socket object but java can set socket options. Maybe a JDBC kong fu
master knows how to do this.
every bit counts
In response to
pgsql-hackers by date
|Next:||From: Marko Tiikkaja||Date: 2010-02-11 13:46:45|
|Subject: Re: Writeable CTEs and empty relations|
|Previous:||From: Dimitri Fontaine||Date: 2010-02-11 13:41:15|
|Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL|