| From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Index bloat of 4x |
| Date: | 2007-01-17 17:52:03 |
| Message-ID: | 20070117125203.899f6660.wmoran@collaborativefusion.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In response to Alvaro Herrera <alvherre(at)commandprompt(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-01-17 17:53:44 | Re: Controlling memory of session |
| Previous Message | novnov | 2007-01-17 17:41:03 | Re: Speed of postgres compared to ms sql, is this article/comment |