From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Tarabas (Manuel Rorarius)" <tarabas(at)tarabas(dot)de> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [bulk] Re: Non returning Transactions/Many Locks in Postgres 9.0.4 and 9.0.1 |
Date: | 2011-06-08 14:38:08 |
Message-ID: | BANLkTik36muCVfLxARcK3vMyFWOYgOgufA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jun 8, 2011 at 9:32 AM, Tarabas <tarabas(at)tarabas(dot)de> wrote:
> Hello,
>
> the problem just resurfaced and the Wiki page dows not really help
> very much.
>
> When i look into the pg_stat_activity, i only see that the connections
> all state "<IDLE> in transaction".
>
> Is there any way to find out what the transaction is doing exactly to
> be able to debug the Problem?
The transactions aren't doing anything. Your applciation began
transactions in your application but didn't commit them. Classic
causes of this are:
1) straight up bugs (code branches that do not commit)
2) multi threaded code, especially when threads share connections
(basically a factory for #1 above)
3) busted connection poolers (php_pconnect)
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2011-06-08 16:14:27 | Re: Abnormal long SELECT query under postgresql 9.0.4 |
Previous Message | Tarabas | 2011-06-08 14:32:54 | Re: [bulk] Re: Non returning Transactions/Many Locks in Postgres 9.0.4 and 9.0.1 |