Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal - Mailing list pgsql-performance

From Chris Browne
Subject Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal
Date
Msg-id 608xbotve5.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal  (Guillaume Cottenceau <gc@mnc.ch>)
Responses Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal  (Michael Stone <mstone+postgres@mathom.us>)
List pgsql-performance
mstone+postgres@mathom.us (Michael Stone) writes:
> On Wed, May 16, 2007 at 12:09:26PM -0400, Alvaro Herrera wrote:
>>Maybe, but we should also mention that CLUSTER is a likely faster
>>workaround.
>
> Unless, of course, you don't particularly care about the order of
> the items in your table; you might end up wasting vastly more time
> rewriting tables due to unnecessary clustering than for full vacuums
> on a table that doesn't need it.

Actually, this is irrelevant.

If CLUSTER is faster than VACUUM FULL (and if it isn't, in all cases,
it *frequently* is, and probably will be, nearly always, soon), then
it's a faster workaround.
--
output = ("cbbrowne" "@" "linuxfinances.info")
http://cbbrowne.com/info/oses.html
"What if you slept?  And what if, in your sleep, you dreamed?
 And what if, in your dream, you went to heaven and there
 plucked a strange and beautiful flower?  And what if, when
 you awoke, you had the flower in your hand?  Ah, what then?"
    --Coleridge

pgsql-performance by date:

Previous
From: Michael Stone
Date:
Subject: Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal
Next
From: Michael Stone
Date:
Subject: Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal