Search Postgresql Archives

Re: VACUUM hanging on PostgreSQL 8.3.1 for larger tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello

If Your 'vacuum verbose analyze table' ends pretty fast,and Your 'vacuum full verbose analyze table' never ends,watch for 'select count (*) from pg_locks',might be that You have some heavy load transaction processing on that table,so 'vacuum full....' wait for transactions to end. If possible kill all processes that access that table and try 'vacuum full verbose analyze table'. Anyway,if processor is mostly idle,always check 'select count (*) from pg_locks' , at least in my experience.

Sincerely

Dragan Zubac

Tom Lane wrote:
"Paragon" <lr@xxxxxxxx> writes:
Right now I have vacuum_cost_delay = 600

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.

			regards, tom lane




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux