On Thu, 10 Apr 2008, Art Gramlich wrote:
> They do. We usually have different connection pools for normal (short
> running) and long queries. Since almost all are short running, this has
> worked well for us. I actually haven't tried setting keepalive in this
> situation. so I can't say much, but the vpn solutions we have used have at
> times gotten into some pretty wierd states and sotimeouts could stop our
> pools from going crazy.
I can see how keepalives are generally useful while sotimeouts are only
useful in the specific situation where you can set a global limit on your
query times. On the other hand the sotimeout is configurable while the
keepalive timeout isn't configurable (at least in Java). I'm not
particularly excited about either option, but I don't need them either.
I don't see a danger with exposing them as options as long as the pros
and cons are clearly explained.
In response to
pgsql-jdbc by date
|Next:||From: Art Gramlich||Date: 2008-04-11 17:02:53|
|Subject: Re: Patch to add a socketTimeout property.|
|Previous:||From: John R Pierce||Date: 2008-04-10 23:52:15|
|Subject: Re: Problem with very big queries.|