Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3A6679FB2AD for ; Wed, 17 Jan 2007 13:13:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 87391-10 for ; Wed, 17 Jan 2007 13:12:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 5F7A39FB2AB for ; Wed, 17 Jan 2007 13:12:55 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-100-202.bk7-dsl.surnet.cl [200.126.100.202]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l0HHCs3T001018; Wed, 17 Jan 2007 09:12:54 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 49A5932A0B; Wed, 17 Jan 2007 14:12:51 -0300 (CLST) Date: Wed, 17 Jan 2007 14:12:51 -0300 From: Alvaro Herrera To: Bill Moran Cc: pgsql-general@postgresql.org Subject: Re: Index bloat of 4x Message-ID: <20070117171251.GH26080@alvh.no-ip.org> Mail-Followup-To: Bill Moran , pgsql-general@postgresql.org References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com> <20070117154251.GG26080@alvh.no-ip.org> <20070117113216.a6d72185.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070117113216.a6d72185.wmoran@collaborativefusion.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 17 Jan 2007 09:12:55 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/911 X-Sequence-Number: 107451 Bill Moran wrote: > The entire database was around 28M prior to the upgrades, etc. Immediately > after the upgrades, it was ~270M. Following a vacuum full, it dropped to > 165M. Following a database-wide reindex, it dropped to 30M. Oh, so it was clearly the upgrade procedure that caused the bloat ... Reindexing seems the expected course. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support