Thread: More VACUUM output?

First of all, Tom, thanks a lot for your repsonse!
It helps...
I have one more question (it is the same damn command - still running,
since Tuesday morning!):

NOTICE:  --Relation dnb--
NOTICE:  Index duns_idx: Pages 587975; Tuples 180289753: Deleted 13980845.
        CPU 268.47s/781.13u sec elapsed 3570.69 sec.
NOTICE:  Index sic_idx: Pages 553200; Tuples 180290790: Deleted 13980845.
        CPU 322.57s/743.92u sec elapsed 13081.00 sec.
NOTICE:  Index state_idx: Pages 699828; Tuples 156813148: Deleted 13980845.
        CPU 392.50s/735.70u sec elapsed 15806.45 sec.
NOTICE:  Index dnb_gist_idx: Pages 695689; Tuples 180297513: Deleted
13980845.
        CPU 408.83s/744.99u sec elapsed 16559.23 sec.
NOTICE:  Removed 13980845 tuples in 216626 pages.
        CPU 111.51s/104.37u sec elapsed 1352.91 sec.
NOTICE:  Index duns_idx: Pages 587978; Tuples 166317982: Deleted 13980846.
        CPU 232.80s/686.22u sec elapsed 3645.48 sec.
NOTICE:  Index sic_idx: Pages 553206; Tuples 166318925: Deleted 13980846.
        CPU 258.04s/636.63u sec elapsed 10390.20 sec.
NOTICE:  Index state_idx: Pages 699834; Tuples 142839792: Deleted 13980846.
        CPU 329.00s/646.69u sec elapsed 14384.46 sec.

What does this mean? Has it started over? Why?
Is it ever going to finish?

Thanks a lot!

Dima

Dmitry Tkach <dmitry@openratings.com> writes:
> What does this mean? Has it started over? Why?

No, it's just taking the dead tuples it's got so far and deleting them
from the indexes.  It does that whenever it's got VACUUM_MEM worth of
dead tuples collected.  You might be able to make things go a little
faster by increasing VACUUM_MEM ... but I wouldn't recommend aborting
the job at this point.

> Is it ever going to finish?

Looks like it's making progress to me.

            regards, tom lane