Re: New VACUUM FULL - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: New VACUUM FULL
Date
Msg-id 4B644467.8080506@enterprisedb.com
Whole thread Raw
In response to Re: New VACUUM FULL  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> On Wed, 2010-01-06 at 14:41 +0900, Takahiro Itagaki wrote:
> 
>> I just applied the patch with a few additional comments.
> 
> I just realised that this new feature *removes* any clustering that was
> previously defined on a table.

Hmm, that's an overstatement. If the table was in order before, it will
be in the same order after VACUUM FULL, all empty gaps and dead tuples
are just removed. It also doesn't clear the indisclustered field in
pg_index, so the next time you run CLUSTER it will cluster the table
just fine.

I'm guessing that you mean that VACUUM FULL doesn't reorder the table
like CLUSTER does. I think that's OK, it has never done that. In fact
the current situation is already an improvement, the new VACUUM FULL
doesn't reshuffle the table and destroy old ordering like the old one does.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tim Bunce
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl UPDATE v3 [PATCH]
Next
From: Tim Bunce
Date:
Subject: Re: Package namespace and Safe init cleanup for plperl [PATCH]