On Fri, Mar 27, 2009 at 9:07 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > Or take it further back still and think about why "idle in transaction" > occurs at all and fix *that*. Maybe not in Postgres at all, possibly in > the driver or even higher up client stack.
>From my experience, the main reasons for this problem are: - a poorly coded connection pool (a lot of people think they really should write their connection pooling solution themselves...); - a poorly coded application; - bugs in the code. So you really should try to fix them in your application first. That said, I have one case in mind where I wasn't able to fix completely the connection pool and the application and we still encounter idle in transaction connections from time to time. For this sort of case, a timeout would be a nice solution. -- Guillaume -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
