Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 0A3329FA242 for ; Wed, 31 Oct 2007 21:09:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 25639-06 for ; Wed, 31 Oct 2007 21:08:44 -0300 (ADT) Received: from mx3.hub.org (mx3.hub.org [206.223.169.73]) by postgresql.org (Postfix) with ESMTP id 37D1B9FA0F9 for ; Wed, 31 Oct 2007 21:09:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx3.hub.org (Postfix) with ESMTP id 7C560380AFD for ; Wed, 31 Oct 2007 21:09:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lA101V1J023307; Wed, 31 Oct 2007 20:01:32 -0400 (EDT) To: "Scott Marlowe" cc: "Achilleas Mantzios" , pgsql-admin@postgresql.org, "Patrick De Zlio" Subject: Re: How to kill process "idle in transaction" In-reply-to: References: <58729a240710300145m4457f63euc15007893e8a805c@mail.gmail.com> <200710301111.02475.achill@matrix.gatewaynet.com> Comments: In-reply-to "Scott Marlowe" message dated "Wed, 31 Oct 2007 16:47:28 -0500" Date: Wed, 31 Oct 2007 20:01:31 -0400 Message-ID: <23306.1193875291@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/329 X-Sequence-Number: 27243 "Scott Marlowe" writes: > On 10/30/07, Achilleas Mantzios 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, 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