In article <424AEB5D.2090204@xxxxxxxxxxx>,
Adam Siegel <adam@xxxxxxxxxxx> wrote:
[...]
% We perform a vacuum full after each mass delete. This cycle can happen
% many times during over a couple of weeks. We are in a test lab
% environment and are generating a lot of data.
%
% One of the problems we have is that the vacuum on the table can take up
% to 10 hours. We also expect to see the physical disk space go down, but
% this does not happen.
Try vacuum full verbose next time to see what it's doing.
Try reindexing after the vacuum is done.
You may find an ordinary vacuuum is faster and just as useful as vacuum full
assuming you're filling and deleting from the same table all the time. It
won't free up space, but it will allow you to maintain a high-water mark.
Look at the relpages column in pg_class to see which relations are using
up the most space.
If you're clearing out all the data for a set of tables, drop them and
recreate them.
--
Patrick TJ McPhee
North York Canada
ptjm@xxxxxxxxxxxx
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
