Re: Re: Name for new VACUUM

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Name for new VACUUM
Date: 2001-08-05 18:00:38
Message-ID: 3B6D89C6.172313F9@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> > Just out of curiosity - does CLUSTER currently "practically rebuild
> > a tables representation" ?
>
> CLUSTER currently *loses* most of a table's representation :-(.
> It needs work.

at least \h CLUSTER in psql seems to imply that it is OK to use CLUSTER
?

Do we have some indication of last CLUSTER command (like an OID column
of
cluster index field) in pg_relation so that VACUUM caould make better
decisions when moving tuples ?

> But since the whole point of CLUSTER is to physically rearrange the
> tuples of a table, it seems to me that it's in a different category
> from VACUUM anyway.

Another way to look at it is as "VACUUM LOCK AND PERFORM HEAVY
REARRANGEMENTS"

Or does the current implementation actually do the rearrangement by
appending all out-of-index-order tuples to the end and _not_ clean up
unused space requiring an additional vacuum after CLUSTER ?

--------------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-08-05 18:10:58 Re: Re: Name for new VACUUM
Previous Message Hannu Krosing 2001-08-05 17:52:00 Re: Idea for nested transactions / savepoints