Thread: VACUUM FULL cannot be VERBOSE?

hi,

is it correct behavior that when i issue command "VACUUM VERBOSE", i get
output with DETAIL info, but when i issue "VACUUM FULL VERBOSE", no
details are displayed?

here are some samples:

VACUUM VERBOSE;
INFO:  vacuuming "pg_catalog.pg_type"
INFO:  scanned index "pg_type_oid_index" to remove 540 row versions
DETAIL:  CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  scanned index "pg_type_typname_nsp_index" to remove 540 row versions
DETAIL:  CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  "pg_type": removed 540 row versions in 3 pages
DETAIL:  CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  index "pg_type_oid_index" now contains 880 row versions in 6 pages
DETAIL:  540 index row versions were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.

VACUUM FULL VERBOSE;
INFO:  vacuuming "pg_catalog.pg_type"
INFO:  vacuuming "pg_catalog.pg_attribute"
INFO:  vacuuming "pg_catalog.pg_statistic"
INFO:  vacuuming "public.accountingitemaccounts"
INFO:  vacuuming "public.accountingcategories"
INFO:  vacuuming "public.accountingitems"

i'm using postgresql 9.0.4 on gentoo linux. i tried postgresql
documentation, google, as well as searching postgresql mailing list but
found no info on this, so sorry if this is duplicate question or obvious
thing.

miroslav

2011/6/30 Miroslav Šulc <miroslav.sulc@startnet.cz>:
> is it correct behavior that when i issue command "VACUUM VERBOSE", i get
> output with DETAIL info, but when i issue "VACUUM FULL VERBOSE", no
> details are displayed?

Yes, this seems OK. PostgreSQL 9.0 has a new implementation of VACUUM
FULL, which behaves more like CLUSTER. This new implementation doesn't
account statistics like a normal VACUUM VERBOSE does.

It seems that PostgreSQL 9.1 re-adds these stats to VACUUM FULL VERBOSE.

Regards,
Marti