From: | Lewis Kapell <lkapell(at)setonhome(dot)org> |
---|---|
To: | Vladimir Rusinov <vladimir(at)greenmice(dot)info> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: fighting '<IDLE> in transaction' |
Date: | 2009-11-03 14:54:12 |
Message-ID: | 4AF04414.4050404@setonhome.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Please see these earlier threads:
Is IDLE session really idle?
http://archives.postgresql.org/pgsql-admin/2009-06/msg00096.php
Idle connections
http://archives.postgresql.org/pgsql-admin/2009-10/msg00017.php
Lewis Kapell
Vladimir Rusinov wrote:
> Hi!
>
> We are having a lot of '<IDLE> in transaction' processes in production
> database. This does not seems to be big problem now, since they are not
> taking any big locks. But I'm aware that sometime it can become a
> problem. Currently I'm just killing all processes that are in 'idle in
> transaction' for more than 1 minute.
>
> Our application is quite big and complex, so it's not easy to find peace
> of code where it happens. How can I get transaction history for
> processes that idle in transaction to send it to developers so they can
> find problem in code.
>
> We are running postgresql 8.3 with query logging off (turning it on
> causes performance disaster). Application is run under jboss and AFAIK
> uses hibernate.
>
> --
> Vladimir Rusinov
> http://greenmice.info/
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-11-03 18:10:57 | Re: Need help in enabling remote connection |
Previous Message | Vladimir Rusinov | 2009-11-03 11:31:17 | fighting '<IDLE> in transaction' |