On 03/02/2016 02:49 PM, Tom Lane wrote:
Or maybe the problem was that when we forced track_counts off because of
no stats collector, we didn't emit any bleat noting that, which if we had
might have led you to realize that the above messages were the direct
cause of the next one:
2016-03-02 14:58:09 EST [14366]: [10-1] WARNING: autovacuum not started because of misconfiguration
2016-03-02 14:58:09 EST [14366]: [11-1] HINT: Enable the "track_counts" option.
Or both changes, or something else entirely?
I'd be interested to hear how you perceived these log messages and
what you think might help the next person.
I can tell you that as I read them, they meant nothing and I know what
they mean. This is why:
2016-03-02 14:58:09 EST [14366]: [8-1] LOG: could not resolve
"localhost": Name or service not known
2016-03-02 14:58:09 EST [14366]: [9-1] LOG: disabling statistics
collector for lack of working socket
Why would I care about a "LOG" message. Generally speaking they don't
tell us anything useful. If, it was:
ERROR: could not resolve "localhost" ...
ERROR: Disabling statistics collector ....
It would mean a whole lot more. The second set makes sense to me but
what isn't clear is that the first one is really an error that can cause
the warnings of the second.
I do think that it should be an error if we are disabling statistics due
to something being wrong. We can't really operate properly without them.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
