Re: Upgrading postmaster's log messages about bind/listen errors
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Euler Taveira <euler@timbira.com.br>, Robert Haas <robertmhaas@gmail.com>,
Joe Conway <mail@joeconway.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-03-10T20:32:46Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Tom Lane wrote: >> 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. > Well, you could take a broken 9.3 installation and pg_upgrade it to > pg10. It wouldn't be any less broken. Sure, but does the rest of the world need to keep looking at this message? Anybody who's actually in that situation probably never looks at the postmaster log at all. I think that what would actually be of some use nowadays is a LOG-level message emitted if the wraparound *isn't* activated immediately at start. But otherwise, we should follow the rule that silence is golden. regards, tom lane
Commits
-
Make logging about multixact wraparound protection less chatty.
- 5ed6fff6b729 10.0 landed
-
Improve postmaster's logging of listen socket creation.
- f9dfa5c97766 10.0 landed
-
Reduce log verbosity of startup/shutdown for launcher subprocesses.
- 6ec4c8584c45 10.0 landed