"Paragon" <lr(at)pcorp(dot)us> writes:
>> Is it actually *doing* anything, like consuming CPU or I/O -- and if so
>> which? How much does VACUUM VERBOSE print before getting stuck?
> --If I start the
> vacuum verbose ky.ky_edges;
> and monitor vmstat 1 looks like this
Sure looks like a near-idle machine to me :-(.
I think that the vacuum must be stuck on a lock. What other Postgres
processes have you got, and what are they doing?
regards, tom lane