From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: New VACUUM FULL |
Date: | 2009-12-15 09:05:26 |
Message-ID: | 20091215180526.93E3.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here is an updated patch rebased to the latest CVS HEAD.
One remaining concern is VERBOSE. Log messages by FULL (rewrite) are less
verbose than FULL INPLACE. The same can be said for CLUSTER VERBOSE, though.
I don't have any plans to make CLUSTER more verbose in the patch, but
"more verbose CLUSTER" could be a TODO item.
=# VACUUM (FULL, VERBOSE) pgbench_accounts;
INFO: vacuuming "public.pgbench_accounts"
VACUUM
=# VACUUM (FULL INPLACE, VERBOSE) pgbench_accounts;
INFO: vacuuming "public.pgbench_accounts"
INFO: "pgbench_accounts": found 0 removable, 100000 nonremovable row versions in 1640 pages
DETAIL: 0 dead row versions cannot be removed yet.
Nonremovable row versions range from 128 to 128 bytes long.
There were 0 unused item pointers.
Total free space (including removable row versions) is 195520 bytes.
0 pages are or will become empty, including 0 at the end of the table.
1 pages containing 5396 free bytes are potential move destinations.
CPU 0.00s/0.01u sec elapsed 0.01 sec.
INFO: index "pgbench_accounts_pkey" now contains 100000 row versions in 276 pages
DETAIL: 0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: "pgbench_accounts": moved 0 row versions, truncated 1640 to 1640 pages
DETAIL: CPU 0.00s/0.00u sec elapsed 0.00 sec.
VACUUM
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
vacuum-full_20091215.patch | application/octet-stream | 41.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2009-12-15 09:30:59 | Re: ECPG patch 2, SQLDA support |
Previous Message | Fred Janon | 2009-12-15 08:38:07 | Fwd: pgAdmin III: timestamp displayed in what time zone? |