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: Stephen Frost <sfrost@snowman.net>
Cc: Tels <nospam-pg-abuse@bloodgate.com>, Robert Haas <robertmhaas@gmail.com>,
Joe Conway <mail@joeconway.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-03-10T16:36:20Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > * Tom Lane (tgl@sss.pgh.pa.us) wrote: >> ... So I think the logging setup I had in >> my patch is pretty much the only sane way to do it, and we just have >> to decide whether it's worth exposing at default log level or not. > I definitely think we should include it at the default log level. We > certainly wouldn't be the first daemon process to do so (bind9 comes to > mind, but I notice ntpd, nrpe, and strongswan do also, and probably some > others). I'm leaning in that direction as well now. I think we could address Robert's concern about startup chattiness by downgrading the other mentioned messages to DEBUG1. I will check, but I'm pretty sure that there is already adequate logging for subprocess startup failure --- and if there is not, that would be a bug in itself. 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