Re: vacuumdb question/problem

Simon Riggs <simon@2ndQuadrant.com> writes:
> On Fri, Jul 15, 2011 at 5:10 PM, David Ondrejik <David.Ondrejik@noaa.gov> wrote:
>> Since then, the process has continued to run (for about 20 hrs) without any
>> additional information being returned.

> Probably locked behind another long running task that is holding a buffer pin.

That's possible, or it could be busy vacuuming some (really large?)
index.  Is the process actually busy, as in consuming CPU time according
to top or other process monitoring tool?

            regards, tom lane