X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 49F039FB3F2
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Sat,  2 Sep 2006 05:37:33 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 96227-01 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Sat,  2 Sep 2006 05:37:27 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from folium.sgala.coma (fw-nat.workzone.ovus.it [83.211.167.226])
	by postgresql.org (Postfix) with ESMTP id DF79C9FB3C8
	for <pgsql-performance@postgresql.org>;
	Sat,  2 Sep 2006 05:37:27 -0300 (ADT)
Received: by folium.sgala.coma (Postfix, from userid 1000)
	id 962E82FA887; Sat,  2 Sep 2006 10:37:25 +0200 (CEST)
Date: Sat, 2 Sep 2006 10:37:25 +0200
From: Matteo Sgalaberni <sgala@sgala.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: database bloat, non removovable rows,
 slow query etc... [RESOLVED]
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12756.1157132120@sss.pgh.pa.us>
X-Operating-System: Linux folium 2.4.20-3-686
User-Agent: Mutt/1.5.11+cvs20060126
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.16 tagged_above=0 required=5 tests=AWL,
	FORGED_RCVD_HELO
X-Spam-Level: 
X-Archive-Number: 200609/13
X-Sequence-Number: 20699

On Fri, Sep 01, 2006 at 01:35:20PM -0400, Tom Lane wrote:
> Matteo Sgalaberni <sgala@sgala.com> 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).

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