> This means that
> 
> VACUUM FULL mytable; 
> 
> would translate to:
> 
> VACUUM mytable;  -- make free space
> COMPACT mytable; -- move tuples in a bunch of small transactions
>                  -- might have a GUC for max trx length
> VACUUM mytable;  -- free the tuples at the end and give space back to fs


VACUUM my table [n] tuples; -- free tuples at the end but only up to [n]
tuples.


Joshua D. Drake


-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

In response to

• Re: Revitalising VACUUM FULL for 8.3 at 2007-03-01 12:42:51 from Hannu Krosing

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2007-03-01 16:00:55
	Subject: Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ?
Previous:	From: Jim C. Nasby	Date: 2007-03-01 15:45:00
	Subject: Re: Dead Space Map version 2