|From:||Michael Stone <mstone+postgres(at)mathom(dot)us>|
|Subject:||Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Wed, May 16, 2007 at 03:34:42PM -0400, Chris Browne wrote:
>mstone+postgres(at)mathom(dot)us (Michael Stone) writes:
>> 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.
I think it's perfectly relevant.
>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.
Cluster reorders the table. If a table doesn't have any dead rows and
you tell someone to run cluster or vacuum full, the vaccuum basically
won't do anything and the cluster will reorder the whole table. Cluster
is great for certain access patterns, but I've been noticing this odd
tendency lately to treat it like a silver bullet.
|Next Message||Tom Lane||2007-05-16 21:20:56||Re: [DOCS] Autovacuum and XID wraparound|
|Previous Message||Alvaro Herrera||2007-05-16 21:05:32||Re: [DOCS] Autovacuum and XID wraparound|
|Next Message||Alvaro Herrera||2007-05-16 21:25:50||Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal|
|Previous Message||Chris Browne||2007-05-16 19:34:42||Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal|