Skip site navigation (1) Skip section navigation (2)

Re: Idle transactions

From: Tino Schwarze <postgresql(at)tisc(dot)de>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Idle transactions
Date: 2007-09-11 11:39:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Tue, Sep 11, 2007 at 11:15:54AM +0000, Mateus Interciso wrote:

> Hello, it's been a while that I'm seeing that our servers running JBoss 
> with PostgreSQL, after some hours of work, have at least 70 or more 
> "<IDLE> in transaction" status for transactions, and this is bogging down 
> our servers.
> Is this normal behaviour? If not, is there anything I can do to prevent 
> it? Why is it happening? What's a transaction that is "<IDLE> in 
> transaction" actually really means?

"idle in transaction" means that someone did a "begin", but didn't issue
a "commit" or "rollback" yet. It is often a sign of bad application
design and you should contact the application developers. Since open
transactions may hold locks on tables, the whole application may stop
unexpectedly if transactions are left open.

Another possibility is that you've just got a huge workload, e.g. lots
of concurrent access to the application so that it has to perform a lot
of work, but then you should see SELECT/INSERT/UPDATE/etc. as well, not
only "idle in transaction".

In Java terms, code which uses a transaction should always look like
boolean success = false; // default: roll back, e.g. on Exception
  // perform work
  success = true;
   connection.closeTransaction (success);




Tino Schwarze * Parkstra├če 17h * 09120 Chemnitz

In response to


pgsql-admin by date

Next:From: Mateus IntercisoDate: 2007-09-11 12:26:18
Subject: Re: Idle transactions
Previous:From: Thomas MarkusDate: 2007-09-11 11:37:09
Subject: Re: Idle transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group