public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Guillaume Cottenceau <[email protected]>
Cc: Jim C. Nasby <[email protected]>
Cc: Michael Stone <[email protected]>
Cc: [email protected]
Subject: Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal
Date: Wed, 16 May 2007 12:09:26 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Guillaume Cottenceau wrote:
> "Jim C. Nasby" <decibel 'at' decibel.org> writes:
> 
> > On Wed, May 16, 2007 at 09:41:46AM +0200, Guillaume Cottenceau wrote:
> 
> [...]
> 
> > > Come on, I don't suggest to remove several bold warnings about
> > > it, the best one being "Therefore, frequently using VACUUM FULL
> > > can have an extremely negative effect on the performance of
> > > concurrent database queries." My point is to add the few
> > > additional mentions; I don't think the claims that VACUUM FULL
> > > physically compacts the data, and might be useful in case of too
> > > long time with infrequent VACUUM are incorrect, are they?
> > 
> > Unfortunately they are, to a degree. VACUUM FULL can create a
> > substantial amount of churn in the indexes, resulting in bloated
> > indexes. So often you have to REINDEX after you VACUUM FULL.
> 
> Ok, VACUUM FULL does his job (it physically compacts the data and
> might be useful in case of too long time with infrequent VACUUM),
> but we are going to not talk about it because we often needs a
> REINDEX after it? The natural conclusion would rather be to
> document the fact than REINDEX is needed after VACUUM FULL, isn't
> it?

Maybe, but we should also mention that CLUSTER is a likely faster
workaround.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

view thread (13+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox