| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tuning autovacuum |
| Date: | 2011-10-14 16:59:54 |
| Message-ID: | 4E986A8A.8090302@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Ideally we would have something like checkpoint_warning that warns users
> in the log when there are too few autovacuum workers and cleanup is
> being delayed.
I don't think that any table-stats based approach is going to work. I
think you need to measure the queue of tables which need autovacuuming.
So you do something like:
If > 10% of tables and > 10 tables need autovac/autoanalyze for more
than one polling interval in a row, then emit a warning.
Note that there are solutions other than adding workers; the user could
also lower the polling interval, decrease vacuum_delay, or do other
things to make autovac faster.
This would require tracking stats about the size of the autovac queue.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2011-10-14 17:13:06 | Re: Core Extensions relocation |
| Previous Message | Josh Berkus | 2011-10-14 16:52:32 | Call stacks and RAISE INFO |