pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: vacuum process taking more than 33 hours
Date: Mon, 15 Jan 2007 09:53:16 -0500
Message-ID: <20070115145316.GC13011@phlogiston.dyndns.org> (raw)
In-Reply-To: <86aad3420701150644j5beef392q7007324f3d7008a@mail.gmail.com>
References: <2529.5826.qm@web30013.mail.mud.yahoo.com>
	<20070115143247.GA13011@phlogiston.dyndns.org>
	<86aad3420701150644j5beef392q7007324f3d7008a@mail.gmail.com>

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



view thread (4+ messages)

Message-ID: <20070115145316.GC13011@phlogiston.dyndns.org>
Permalink:  ../20070115145316.GC13011@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20070115145316.GC13011@phlogiston.dyndns.org

 · 

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-sql@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: vacuum process taking more than 33 hours
  In-Reply-To: <20070115145316.GC13011@phlogiston.dyndns.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