Re: syslogging oddity - Mailing list pgsql-hackers

From Tom Lane
Subject Re: syslogging oddity
Date
Msg-id 7285.1185149112@sss.pgh.pa.us
Whole thread Raw
In response to syslogging oddity  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: syslogging oddity  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Somewhere along the way we seem to have made the syslogger's shutdown 
> message go to stderr, even if we have redirected it:

I'm pretty sure it has done that all along; at least the design
intention is that messages generated by syslogger itself should go to
its stderr.  (Else, if the logger is having trouble, you might never get
to find out why at all.)

It might be reasonable to reduce "logger shutting down" to DEBUG1
or so, now that the facility has been around for awhile.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: syslogging oddity
Next
From: Magnus Hagander
Date:
Subject: Re: syslogging oddity