| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Rob Richardson" <Rob(dot)Richardson(at)rad-con(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Autovacuum not started because of misconfiguration |
| Date: | 2010-11-03 20:01:23 |
| Message-ID: | 16780.1288814483@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Rob Richardson" <Rob(dot)Richardson(at)rad-con(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-11-03 20:03:31 | Re: Autovacuum not started because of misconfiguration |
| Previous Message | Rob Richardson | 2010-11-03 19:28:48 | Autovacuum not started because of misconfiguration |