From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Upgrading postmaster's log messages about bind/listen errors |
Date: | 2017-03-11 06:34:17 |
Message-ID: | CAMsr+YG_-EJVxHjCk0ag4C5oegGx356+QNWE=JE37LecSC9qSA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 March 2017 at 03:24, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Sontakke | 2017-03-11 10:26:25 | Re: Speedup twophase transactions |
Previous Message | Craig Ringer | 2017-03-11 06:32:08 | Re: [PATCH] Transaction traceability - txid_status(bigint) |