Re: New VACUUM FULL
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
Date: 2009-11-12T13:13:56Z
Lists: pgsql-hackers
Itagaki Takahiro wrote: > Here is a patch to support "rewrite" version of VACUUM FULL. > It was called "VACUUM REWRITE" in the past disucussin, > but I choose the following syntax for now: > > VACUUM ( FULL [ INPLACE | REPLACE ] ) [ table_name ] > > The reason is to contrast the new REPLACE behavior with the old INPLACE > behavior. I cannot find any good terms of opposite meaning of REWRITE. I thought the idea is to rip out the current implementation altogether. If that's the case, then it doesn't make sense to use a different syntax. Just rip the innards of VACUUM FULL and replace them with your new implementation. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.