X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id DF34A9FB504 for ; Sat, 2 Sep 2006 11:16:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 34181-06 for ; Sat, 2 Sep 2006 14:16:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by postgresql.org (Postfix) with SMTP id 48AB99FB503 for ; Sat, 2 Sep 2006 11:16:39 -0300 (ADT) Received: (qmail 28357 invoked from network); 2 Sep 2006 14:16:38 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.2?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 2 Sep 2006 14:16:38 -0000 In-Reply-To: <20060902083725.GB2266@sgala.com> References: <20060901123915.GT2266@sgala.com> <4027.1157121810@sss.pgh.pa.us> <20060901172829.GX2266@sgala.com> <12756.1157132120@sss.pgh.pa.us> <20060902083725.GB2266@sgala.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Tom Lane , pgsql-performance@postgresql.org Content-Transfer-Encoding: 7bit From: Dave Cramer Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED] Date: Sat, 2 Sep 2006 10:16:36 -0400 To: Matteo Sgalaberni X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/14 X-Sequence-Number: 20700 Matteo, On 2-Sep-06, at 4:37 AM, Matteo Sgalaberni wrote: > On Fri, Sep 01, 2006 at 01:35:20PM -0400, Tom Lane wrote: >> Matteo Sgalaberni writes: >>> Ok. I stopped all clients. No connections to this database. >> >> When you say "this database", do you mean the whole postmaster >> cluster, >> or just the one database? Open transactions in other databases of >> the >> same cluster can be a problem. >> > AGH!!!! AGHR!!! > > A my collegue JDBC application that stay in "idle intransaction" > 24h/24h > (but in another database, non in the bloated-reported db...)! > > I killed it now(jdbc app). this behaviour has been fixed in later versions of the jdbc driver > > vacuumed full and PG have cleaned all!! So if I have a idle > transaction in > one database of the cluster it "lock" vacuums of all databases of > the cluster. > > Good to know this...but why this behaviour? it'is lovely...:) > > Tom , can you explain why?... > > Thanks a lot!! > > Matteo > > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster >