From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal |
Date: | 2007-05-16 19:34:42 |
Message-ID: | 608xbotve5.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-performance |
mstone+postgres(at)mathom(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-16 19:44:06 | Re: [DOCS] Autovacuum and XID wraparound |
Previous Message | Alvaro Herrera | 2007-05-16 17:28:50 | Re: [DOCS] Autovacuum and XID wraparound |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Stone | 2007-05-16 21:17:16 | Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal |
Previous Message | Michael Stone | 2007-05-16 16:20:38 | Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal |