From: Bill Moran <wmoran@collaborativefusion.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Index bloat of 4x
Date: Wed, 17 Jan 2007 12:52:03 -0500
Message-ID: <20070117125203.899f6660.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <20070117171251.GH26080@alvh.no-ip.org>
References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com>
<20070117154251.GG26080@alvh.no-ip.org>
<20070117113216.a6d72185.wmoran@collaborativefusion.com>
<20070117171251.GH26080@alvh.no-ip.org>
In response to Alvaro Herrera <alvherre@commandprompt.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.
Right. Sorry if I didn't explain that properly.
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.
--
Bill Moran
Collaborative Fusion Inc.
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: wmoran@collaborativefusion.com, alvherre@commandprompt.com
Subject: Re: Index bloat of 4x
In-Reply-To: <20070117125203.899f6660.wmoran@collaborativefusion.com>
* 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