Re: Does VACUUM reorder tables on clustered indices - Mailing list pgsql-sql

From Chris Browne
Subject Re: Does VACUUM reorder tables on clustered indices
Date
Msg-id 60d5jqja42.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to Does VACUUM reorder tables on clustered indices  (frank church <pgsql@adontendev.net>)
Responses Re: Does VACUUM reorder tables on clustered indices  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Does VACUUM reorder tables on clustered indices  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-sql
jnasby@pervasive.com ("Jim C. Nasby") writes:
> On Wed, Dec 21, 2005 at 12:34:12AM +0100, ipv@tinet.org wrote:
>> Hi,
>> 
>> Utilize <b>CLUSTER;</b> (after vacuum) to reorder the data.
>
> Why would you vacuum when cluster is just going to wipe out the dead
> tuples anyway?

There is one reason to VACUUM before running CLUSTER...

That is that VACUUM will be *guaranteed* to draw all the pages into memory.

Subsequently, you can be certain that the pages are in cache, and that
the CLUSTER should need to do minimal I/O to read data into memory.

If I'm considering clustering the Slony-I "sl_log_1" table, forcing it
into memory *is* something I'll consider doing in order to minimize
the time that would-be writers are blocked from writing...
-- 
let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];;
http://cbbrowne.com/info/multiplexor.html
Never criticize anybody until  you have walked  a mile in their shoes,
because by that time you will be a mile away and have their shoes.
-- email sig, Brian Servis


pgsql-sql by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Problem obtaining MAX values FROM TABLE
Next
From: Matthew Smith
Date:
Subject: Re: Help on a complex query (avg data for day of the week)