| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovac hung/blocked |
| Date: | 2006-11-16 17:01:29 |
| Message-ID: | 18763.1163696489@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> On Tuesday November 14 2006 12:56 pm, Jim C. Nasby wrote:
>> You don't have the vacuum cost delay settings set unreasonably
>> high, do you?
> I'm not sure. Here's what we're running:
> autovacuum_vacuum_cost_delay = 500 # default vacuum cost delay for
> # vacuum_cost_delay
> autovacuum_vacuum_cost_limit = 200 # default vacuum cost limit for
> # vacuum_cost_limit
That's unreasonably high --- you're telling autovac to do a little work
(about ten pages' worth) and then sleep for half a second. No wonder it
seems to take forever on a big table. Try autovacuum_vacuum_cost_delay
around 10 or 20 (msec) or so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2006-11-16 17:30:02 | Re: Why the data changes it's value by itself! |
| Previous Message | Tom Lane | 2006-11-16 16:39:01 | Re: can't start postgresql |