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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Semeiks | 2004-08-27 19:02:37 | Re: Foreign keys |
Previous Message | Tom Lane | 2004-08-27 14:34:23 | Re: Storing a plan to disc... |