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

vacuum full 100 mins plus?

From: Patrick Hatcher <PHatcher(at)macys(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: vacuum full 100 mins plus?
Date: 2004-07-14 21:29:48
Message-ID: OF3581B09F.CDD98B1C-ON88256ED1.007318CA-88256ED1.0076E70C@fds.com (view raw or flat)
Thread:
Lists: pgsql-performance



Should I be concerned that my vacuum process has taken upwards of 100 +
minutes to complete?  I dropped all indexes before starting and also
increased the vacuum_mem before starting.
Looking at the output below, it appears that a vacuum full hasn't been done
on this table for quite sometime.  Would I be better off exporting the data
vacuuming the table and reimporting the data?  I cannot drop the table do
to views attached to the table


mdc_oz=# set vacuum_mem = 10240;
SET
mdc_oz=# vacuum full verbose cdm.cdm_ddw_Tran_item;
INFO:  vacuuming "cdm.cdm_ddw_tran_item"
INFO:  "cdm_ddw_tran_item": found 15322404 removable, 10950460 nonremovable
row versions in 934724 pages
DETAIL:  0 dead row versions cannot be removed yet.
Nonremovable row versions range from 233 to 308 bytes long.
There were 1081 unused item pointers.
Total free space (including removable row versions) is 4474020460 bytes.
544679 pages are or will become empty, including 0 at the end of the table.
692980 pages containing 4433398408 free bytes are potential move
destinations.
CPU 29.55s/4.13u sec elapsed 107.82 sec.


TIA
Patrick Hatcher


Responses

pgsql-performance by date

Next:From: Hervé PiedvacheDate: 2004-07-14 21:32:05
Subject: Re: Insert are going slower ...
Previous:From: Hervé PiedvacheDate: 2004-07-14 21:19:16
Subject: Re: Insert are going slower ...

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