From: Craig Ringer <craig@postnewspapers.com.au>
To: Chris <dmagick@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: good old VACUUM FULL
Date: Fri, 01 Apr 2011 11:41:34 +0800
Message-ID: <4D95496E.1050407@postnewspapers.com.au> (raw)
In-Reply-To: <4D89760A.3040109@gmail.com>
References: <AANLkTi=SMx4GiW5DLFTpOm4Go-ibipc6WpTN+4rY7tbF@mail.gmail.com>
<4D89760A.3040109@gmail.com>
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/
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-performance@postgresql.org
Cc: craig@postnewspapers.com.au, dmagick@gmail.com
Subject: Re: good old VACUUM FULL
In-Reply-To: <4D95496E.1050407@postnewspapers.com.au>
* 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