Thread: Autovacuum not started because of misconfiguration

"Rob Richardson" <Rob.Richardson@rad-con.com> writes:
> A customer found this in one PostgreSQL log file:
> EDTWARNING:  autovacuum not started because of misconfiguration

> This has only appeared once.  The database has been restarted since then
> (about eight days ago), and this message has not reappeared.  For now,
> we're not going to worry about it, but I remain curious.  What would
> have caused this, and where would I have looked to find the problem?

The next line should have told you --- it'd have been
HINT: Enable the "track_counts" option.

Now, if you're certain you weren't messing with that parameter setting
throughout this sequence, there might be something worthy of further
investigation here ...

            regards, tom lane

On Wed, Nov 3, 2010 at 1:28 PM, Rob Richardson
<Rob.Richardson@rad-con.com> wrote:
> A customer found this in one PostgreSQL log file:
>
> EDTWARNING:  autovacuum not started because of misconfiguration
> This has only appeared once.  The database has been restarted since then
> (about eight days ago), and this message has not reappeared.  For now, we're
> not going to worry about it, but I remain curious.  What would have caused
> this, and where would I have looked to find the problem?

You don't mention the version of pgsql you're using, that might prove
helpful.  Basically on older pg versions when autovac first showed up
(7.4 or so) you had to turn the stats collector on and block level
stats for it to do its job.  It could be that got turned off for
troubleshooting or something a while back?

My thanks, Tom and Scott.  I'll keep those in mind if the problem shows
up again.

RobR