Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 257D09FB549
	for <pgsql-general-postgresql.org@postgresql.org>;
	Mon, 22 Jan 2007 16:34:27 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024)
	with ESMTP id 06730-05-5 for
	<pgsql-general-postgresql.org@postgresql.org>;
	Mon, 22 Jan 2007 16:34:23 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from alnrmhc11.comcast.net (alnrmhc11.comcast.net [206.18.177.51])
	by postgresql.org (Postfix) with ESMTP id 192AE9FB50A
	for <pgsql-general@postgresql.org>;
	Mon, 22 Jan 2007 16:34:22 -0400 (AST)
Received: from [10.1.2.103]
	(c-75-70-110-235.hsd1.co.comcast.net[75.70.110.235])
	by comcast.net (alnrmhc11) with ESMTP
	id <20070122203244b110016u3ne>; Mon, 22 Jan 2007 20:32:45 +0000
From: "Ed L." <pgsql@bluepolka.net>
To: Csaba Nagy <nagy@ecircle-ag.com>
Subject: Re: Index bloat of 4x
Date: Mon, 22 Jan 2007 13:32:37 -0700
User-Agent: KMail/1.8.1
Cc: Jeremy Haile <jhaile@fastmail.fm>, Tom Lane <tgl@sss.pgh.pa.us>,
	Postgres general mailing list <pgsql-general@postgresql.org>,
	Bill Moran <wmoran@collaborativefusion.com>,
	Alvaro Herrera <alvherre@commandprompt.com>
References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com>
	<1169233408.21922.1170154897@webmail.messagingengine.com>
	<1169457850.2735.20.camel@coppola.muc.ecircle.de>
In-Reply-To: <1169457850.2735.20.camel@coppola.muc.ecircle.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701221332.37953.pgsql@bluepolka.net>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200701/1263
X-Sequence-Number: 107803


We have a large number (50+) of pre-8.2 clusters.  How can I 
best/most easily identify those indices most bloated and in need 
of reindex/rebuilding?

Ed