pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Index bloat of 4x
Date: Thu, 18 Jan 2007 02:08:25 -0500
Message-ID: <19674.1169104105@sss.pgh.pa.us> (raw)
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>

Bill Moran <wmoran@collaborativefusion.com> 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



view thread (25+ messages)  latest in thread

Message-ID: <19674.1169104105@sss.pgh.pa.us>
Permalink:  ../19674.1169104105@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19674.1169104105@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, wmoran@collaborativefusion.com, alvherre@commandprompt.com
  Subject: Re: Index bloat of 4x
  In-Reply-To: <19674.1169104105@sss.pgh.pa.us>

* 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