> Yikes. That's *way* too high. If you're trying to get the vacuum to
complete quickly, it really should be zero anyway. Nonzero is for when you
don't care how >> long vacuum takes as long as it's not sucking too much
I/O from your real work.
Thanks Tom, yap you were right now it runs instan
> 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
Originally I thought it was the autovacuuming getting in the way since I
noticed
>"Paragon" <[EMAIL PROTECTED]> writes:
>> I am running into problems vacuuming my larger tables. It seems for
>> tables greater than 1 million rows, Vacuum just hangs. I could leave it
running
>> for hours and it never comes to completion.
>Is it a
I am running into problems vacuuming my larger tables. It seems for tables
greater than 1 million rows, Vacuum just hangs. I could leave it running
for hours and it never comes to completion.
Things like copying the whole table to a temp table with bulk insert such as
(SELECT * INTO temp FROM
