View Single Post

   
  #7 (permalink)  
Old 04-15-2008, 08:34 PM
Tom Lane
 
Posts: n/a
Default Re: VACUUM hanging on PostgreSQL 8.3.1 for larger tables

"Paragon" <lr@pcorp.us> 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

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply With Quote