David Smith wrote:
>I'll bet money the added, idle postgres connections are just sleeping
>while they wait for work. Given idle connections contribute virtually
>no additional load, don't see his argument that idle connections
>contribute to a database overload. If the minor increase in overhe
Christopher Schultz wrote:
>| Enrico Sadelli wrote:
>| If so, I will set maxIdle="2" and everyone will be happy (especially me :)
>
>That's it! But I suspect that this setting will reduce your performance,
>especially if you have an application with lots of db access and
>sporadic traffic patterns.
Thanks for reply,
>I see you have maxIdle="20". Do you have more that 20 connections
>sitting idle? Is this really that much of a concern? As long as the
>connections are released (closed) and returned to the pool, I don't see
>the problem.
No, I have at most 20 idle connections, that's go
Hi all,
I use tomcat-6.0.14 and postgresql-8.1 with JNDI connection pool, after a
while, my web application (written in Java/JSP), creates many database
connections and postgres processes.
But all of these connections are signed as "Idle", I want to close this idle
connections to avoid getting to g
