From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Mason Hale" <masonhale(at)gmail(dot)com> |
Cc: | "Steve Atkins" <steve(at)blighty(dot)com>, "pgsql-general General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: vacuum taking an unusually long time |
Date: | 2008-07-16 17:17:32 |
Message-ID: | 25342.1216228652@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Mason Hale" <masonhale(at)gmail(dot)com> writes:
>> It looks like "read a page, sleep for 80 milliseconds, repeat".
That's what it looks like to me too.
>> I'd look at your settings for autovacuum_vacuum_cost_limit /
>> autovacuum_vacuum_cost_delay, and maybe the contents of pg_autovacuum.
> autovacuum_vacuum_cost_limit = -1
> autovacuum_vacuum_cost_delay = 20ms
That process is *clearly* not using those vacuum cost parameters ---
it's evidently using a delay of 80ms and some completely over-aggressive
cost settings that're making it sleep for each single page read.
So you need to find out where those whacked-out values are coming from.
pg_autovacuum might be a likely source. Or maybe you just forgot a
SIGHUP after a recent change to postgresql.conf?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Ambler | 2008-07-16 18:17:12 | Re: 10.5 OS X ppc64 problem |
Previous Message | Mason Hale | 2008-07-16 17:08:46 | Re: vacuum taking an unusually long time |