Re: (WIP) VACUUM REWRITE - CLUSTER by ctid
От | Itagaki Takahiro |
---|---|
Тема | Re: (WIP) VACUUM REWRITE - CLUSTER by ctid |
Дата | |
Msg-id | 20091026115417.DBA5.52131E4D@oss.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: (WIP) VACUUM REWRITE - CLUSTER by ctid (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
New VACUUM FULL
|
Список | 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 по дате отправления: