Skip site navigation (1) Skip section navigation (2)

Re: Revitalising VACUUM FULL for 8.3

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Revitalising VACUUM FULL for 8.3
Date: 2007-03-01 15:49:06
Message-ID: 45E6F5F2.4030109@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group