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

Tracking down "idle in transaction" processes

From: Doug Silver <dsilver(at)urchin(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Tracking down "idle in transaction" processes
Date: 2004-08-27 18:12:18
Message-ID: 200408271112.18734.dsilver@urchin.com (view raw or flat)
Thread:
Lists: pgsql-novice
I have recently noticed that there are ~22 postmaster processes that are "idle 
in transaction".  They are definitely caused from a web/Apache process, but I 
can't figure out how to track down the cause.  The pg_stat_activity table 
shows them, but the current_query is empty.  I've seen several questions 
asked about this, but no definitive responses.

I saw from a posting to another list that someone suggested setting 
$dbh->{AutoCommit} = 1; 
immediately after doing a commit.  Is this the proper way to code it?  Would 
not changing the AutoCommit flag cause the "idle in transaction" processes?  
I don't think these were showing up before because I had not enabled the 
Apache::DBI during startup.

This is for Postgres 7.3.2_1 on a FBSD system.

TIA.
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Doug Silver
Urchin Software Corp.	http://www.urchin.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

pgsql-novice by date

Next:From: Jeremy SemeiksDate: 2004-08-27 19:02:37
Subject: Re: Foreign keys
Previous:From: Tom LaneDate: 2004-08-27 14:34:23
Subject: Re: Storing a plan to disc...

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