From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ben <bench(at)silentmedia(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: autovacuum not running |
Date: | 2007-08-29 00:37:12 |
Message-ID: | 16235.1188347832@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ben <bench(at)silentmedia(dot)com> writes:
> Hm, I assumed it wasn't running because pg_stat_all_tables shows the last
> vacuum from several weeks ago, and this is an active db. Also, I see no
> vacuum activity in the logs. But "show autovacuum" does show it being
> on....
Just to double-check, make sure stats_start_collector and
stats_row_level are on, and confirm that you see the stats collector
process in "ps". Also, do you have any of the autovac threshold
parameters at nondefault values?
The autovac process doesn't run continuously, so not seeing it in ps
is not proof that there's a problem. But if pg_stat_all_tables isn't
showing any evidence of vacuums happening, that's probably bad.
> So if it is running after all, how can I track down why things aren't
> getting vacuumed? What log level are the autovacuum logs at?
I think you've gotta crank it up to DEBUG2 or so, which is gonna be
noisy :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2007-08-29 00:42:50 | Re: Is there a better way to do this? |
Previous Message | Alvaro Herrera | 2007-08-29 00:34:05 | Re: Out of Memory - 8.2.4 |