From: Alvaro Herrera <alvherre@commandprompt.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Index bloat of 4x
Date: Wed, 17 Jan 2007 14:12:51 -0300
Message-ID: <20070117171251.GH26080@alvh.no-ip.org> (raw)
In-Reply-To: <20070117113216.a6d72185.wmoran@collaborativefusion.com>
References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com>
<20070117154251.GG26080@alvh.no-ip.org>
<20070117113216.a6d72185.wmoran@collaborativefusion.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: alvherre@commandprompt.com, wmoran@collaborativefusion.com
Subject: Re: Index bloat of 4x
In-Reply-To: <20070117171251.GH26080@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox