Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: How to kill process "idle in transaction"
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
- Cc: "Achilleas Mantzios" <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-admin(at)postgresql(dot)org, "Patrick De Zlio" <pchemla01(at)gmail(dot)com>
- Subject: Re: How to kill process "idle in transaction"
- Date: Wed, 31 Oct 2007 20:01:31 -0400
- Message-id: <23306.1193875291@sss.pgh.pa.us> <text/plain>
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes: > On 10/30/07, Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> wrote: >> Some connection pools issue a BEGIN on the connection just >> after the previous user of the connection issues COMMIT and >> then closes it (Jboss does it). So, <IDLE> in transaction is not >> apriori bad. > You can turn off that behaviour, IIRC. It is broken behaviour as far > as pgsql is concerned, I believe. As of 8.3 it should be harmless, but in existing releases it's bad news. regards, tom lane
- References:
- How to kill process "idle in transaction"
- From: Patrick De Zlio
- Re: How to kill process "idle in transaction"
- From: Achilleas Mantzios
- Re: How to kill process "idle in transaction"
- From: Scott Marlowe
- How to kill process "idle in transaction"
- Prev by Date: Re: Upgrading from 7.2.1 to 8.x
- Previous by thread: Re: How to kill process "idle in transaction"
- Next by thread: [Fwd: Indexes for Foreign Keys?]
- Indexes: