| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tino Schwarze <postgresql(at)tisc(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Vacuum Full |
| Date: | 2009-04-02 00:58:54 |
| Message-ID: | 2259.1238633934@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tino Schwarze <postgresql(at)tisc(dot)de> writes:
>> Maybe we should remove the code and make
>> VACUUM FULL do the table-rewrite thing.
> What do you mean with "the table-rewrite thing", exactly?
Like CLUSTER, except not bothering to sort the rows: just seqscan the
table, enter all live tuples into a new relation file, then rebuild
the indexes from scratch.
The only real disadvantages I can see for this implementation are
that
(1) it won't work on those system catalogs whose relfilenode can't
be reassigned (pg_class and shared catalogs, at least).
(2) it requires extra disk space during the rebuild; although the
argument that VACUUM FULL works in-place is kinda shaky when you
consider its effect on indexes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tino Schwarze | 2009-04-02 08:38:41 | Re: Vacuum Full |
| Previous Message | Tino Schwarze | 2009-04-02 00:24:59 | Re: Vacuum Full |