Autovacuum not started because of misconfiguration - Mailing list pgsql-general

From Rob Richardson
Subject Autovacuum not started because of misconfiguration
Date
Msg-id 04A6DB42D2BA534FAC77B90562A6A03D01615D0B@server.rad-con.local
Whole thread Raw
Responses Re: Autovacuum not started because of misconfiguration
Re: Autovacuum not started because of misconfiguration
List pgsql-general
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?
 
Thanks very much!
 
RobR
 

pgsql-general by date:

Previous
From: Gabriel Dinis
Date:
Subject: Re: PHP Web Auditing and Authorization
Next
From: Tom Lane
Date:
Subject: Re: Autovacuum not started because of misconfiguration