Re: (WIP) VACUUM REWRITE - CLUSTER by ctid - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: (WIP) VACUUM REWRITE - CLUSTER by ctid
Date
Msg-id 20091026115417.DBA5.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: (WIP) VACUUM REWRITE - CLUSTER by ctid  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses New VACUUM FULL
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:

> I got the impression that replacing VACUUM FULL is the most popular
> opinion. I like VACUUM REWRITE myself, except that it would require
> making REWRITE a reserved keyword.

My next proposal for the syntex is "VACUUM (options) table_name".
Since "options" are quoted by '(' and ')', we can add new options
without adding them into reserved keywords.

The traditional vacuum syntax:   VACUUM FULL FREEZE VERBOSE ANALYZE table_name (columns);
will be:   VACUUM (FULL, FREEZE, VERBOSE, ANALYZE) table_name (columns);

I think the syntax is consistent with existing syntex of "EXPLAIN (...)".
We can choose any keyword for the new "rewrite" version.
For example:   * VACUUM ( REWRITE )   * VACUUM ( FULL [ INPLACE | REPLACE ] )

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: License clarification: BSD vs MIT
Next
From: David Fetter
Date:
Subject: Re: License clarification: BSD vs MIT