Re: New VACUUM FULL - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: New VACUUM FULL
Date
Msg-id 20091112131356.GB4780@alvh.no-ip.org
Whole thread Raw
In response to New VACUUM FULL  (Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List 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.


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: write ahead logging in standby (streaming replication)
Next
From: Alvaro Herrera
Date:
Subject: Re: New VACUUM FULL