Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 92A449FB2C9 for ; Thu, 18 Jan 2007 03:08:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 74202-06 for ; Thu, 18 Jan 2007 03:08:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 484339FB2BE for ; Thu, 18 Jan 2007 03:08:28 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l0I78PRU019675; Thu, 18 Jan 2007 02:08:25 -0500 (EST) To: Bill Moran cc: Alvaro Herrera , pgsql-general@postgresql.org Subject: Re: Index bloat of 4x In-reply-to: <20070117125203.899f6660.wmoran@collaborativefusion.com> References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com> <20070117154251.GG26080@alvh.no-ip.org> <20070117113216.a6d72185.wmoran@collaborativefusion.com> <20070117171251.GH26080@alvh.no-ip.org> <20070117125203.899f6660.wmoran@collaborativefusion.com> Comments: In-reply-to Bill Moran message dated "Wed, 17 Jan 2007 12:52:03 -0500" Date: Thu, 18 Jan 2007 02:08:25 -0500 Message-ID: <19674.1169104105@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/953 X-Sequence-Number: 107493 Bill Moran writes: > It wasn't the fact that it bloated that surprised me. It was the > _magnitude_ of bloat that I wasn't expecting, as well as the fact that > it was _all_ _index_ bloat. Um, no, you had plenty of table *and* index bloat before. The problem here is that VACUUM FULL fixed all the table bloat whilst making the index situation worse :-( regards, tom lane