On 11 March 2017 at 03:24, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > On 3/9/17 23:43, Tom Lane wrote: >> However, if we're measuring this on a scale of usefulness to the average >> DBA, I would argue that it's of more interest than any of these messages >> that currently appear by default: >> >> 2017-03-09 23:40:12.334 EST [19335] LOG: MultiXact member wraparound >> protections are now enabled >> 2017-03-09 23:40:12.335 EST [19339] LOG: autovacuum launcher started >> 2017-03-09 23:40:12.336 EST [19341] LOG: logical replication launcher >> started >> >> The first of those is surely past its sell-by date. As for the other two, >> we should log *failure* to start, but not the normal case. > > I'm OK with removing these. No news is good news.
Right, and it doesn't tell us that autovacuum will actually do anything useful. The user could've set ridiculous thresholds/delays, per-table overrides, etc. So it's not much use for remote support/diagnostics, and might as well go away. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
