Re: syslogging oddity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: syslogging oddity
Date: 2007-07-23 00:05:12
Message-ID: 7285.1185149112@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-07-23 07:53:07 Re: syslogging oddity
Previous Message Andrew Dunstan 2007-07-22 23:23:25 COPYable logs