Re: Upgrading postmaster's log messages about bind/listen errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Euler Taveira <euler(at)timbira(dot)com(dot)br>
Cc: 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-10 20:23:08
Message-ID: 15080.1489177388@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Euler Taveira <euler(at)timbira(dot)com(dot)br> writes:
> 2017-03-10 1:43 GMT-03:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> 2017-03-09 23:40:12.334 EST [19335] LOG: MultiXact member wraparound
>> protections are now enabled

> It should be DEBUG1 as soon as 9.3 is deprecated.

Uh, what's that got to do with it? I'm not proposing to downgrade this
message in 9.3, or indeed any current release branch. But it's hard
to believe that a 9.3 installation that had the problem would manage
to make it all the way to a v10 upgrade without the problem having been
fixed. Even if there's one or two incompetent DBAs out there whom
that would apply to, I don't think the rest of the world needs to keep
seeing this message by default.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-03-10 20:24:47 Re: make check-world output
Previous Message Magnus Hagander 2017-03-10 20:18:27 Re: Need a builtin way to run all tests faster manner