the documentation is a little skimpy on the operation of tcpKeepAlive...
we've got a scenario where the java client applications sometimes abort
without cleaning up, and leave a postgres server process just sitting
there. I'm assuming tcpKeepAlive=true would cause these processes to
timeout eventually and clean themselves up? Is this a 2-way keepalive,
in that if the server process dies, the client connection would timeout,
too?
on libpq, there's some options for the keepalive interval and count, but
I don't see any such in JDBC?
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
