Date: Mon, 15 Jan 2007 09:53:16 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: vacuum process taking more than 33 hours
Message-ID: <20070115145316.GC13011@phlogiston.dyndns.org>
References: <2529.5826.qm@web30013.mail.mud.yahoo.com>
	<20070115143247.GA13011@phlogiston.dyndns.org>
	<86aad3420701150644j5beef392q7007324f3d7008a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86aad3420701150644j5beef392q7007324f3d7008a@mail.gmail.com>
User-Agent: Mutt/1.5.9i

On Mon, Jan 15, 2007 at 02:44:15PM +0000, Ezequiel Luis Pellettieri wrote:
> Hi Andrew,
> 
> Why don't you try droping all indexes exept but the constraints ones for
> each table.

I don't have the problem, so I don't know whether that will help.

> then you'll free aprox half of DB size. then re-create indexes,  one by one.
> and finally you can perform a full vacuum.
> 
> that worked for me. :)

On some versions of Postgres, it will, but AFAIK the latest versions
don't have the same index bloat problems.  Moreover, if your vacuum
regime is right, you should _never_ have to VACUUM FULL.

A


-- 
Andrew Sullivan  | ajs@crankycanuck.ca
When my information changes, I alter my conclusions.  What do you do sir?
		--attr. John Maynard Keynes