From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Tels <nospam-pg-abuse@bloodgate.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Upgrading postmaster's log messages about bind/listen errors
Date: Fri, 10 Mar 2017 11:36:20 -0500
Message-ID: <14731.1489163780@sss.pgh.pa.us> (raw)
In-Reply-To: <20170310162722.GG9812@tamriel.snowman.net>
References: <9564.1489091245@sss.pgh.pa.us>
<e3a1715d-dd25-d9bb-4a28-6839c242a2f7@joeconway.com>
<CA+TgmoYpQiZMPHfQX8x8P+RqEq0XQBSb32QHTZ8dDwU+aP3qzg@mail.gmail.com>
<19479.1489121003@sss.pgh.pa.us>
<8371d0860a6019e5630bcdd2a96610ab.squirrel@sm.webmail.pair.com>
<20170310135656.GD9812@tamriel.snowman.net>
<12776.1489160501@sss.pgh.pa.us>
<20170310162722.GG9812@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, nospam-pg-abuse@bloodgate.com, robertmhaas@gmail.com, mail@joeconway.com
Subject: Re: Upgrading postmaster's log messages about bind/listen errors
In-Reply-To: <14731.1489163780@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox