From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tels <nospam-pg-abuse(at)bloodgate(dot)com>, 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 16:36:20 |
Message-ID: | 14731.1489163780@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-03-10 16:38:12 | Re: GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |
Previous Message | Kevin Grittner | 2017-03-10 16:35:37 | Re: GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |