Re: good old VACUUM FULL

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Chris <dmagick(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: good old VACUUM FULL
Date: 2011-04-01 03:41:34
Message-ID: 4D95496E.1050407@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 23/03/2011 12:24 PM, Chris wrote:

> You'll need to reindex that table now - vacuum full can bloat your
> indexes which will affect your other queries.

It doesn't seem to matter much for a one-off. Index bloat problems have
mainly been encountered where people are running VACUUM FULL as part of
routine maintenance - for example, from a nightly cron job.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2011-04-01 06:50:47 Re: COPY with high # of clients, partitioned table locking issues?
Previous Message Joseph Shraibman 2011-04-01 00:41:04 table contraints checks only happen in planner phase