Re: BUG #7559: syslogger doesn't close stdout and stderr - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #7559: syslogger doesn't close stdout and stderr
Date
Msg-id 505CA84B.4090808@gmx.net
Whole thread Raw
In response to Re: BUG #7559: syslogger doesn't close stdout and stderr  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #7559: syslogger doesn't close stdout and stderr  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 9/20/12 11:06 AM, Tom Lane wrote:
> Well, I would have no objection to changing pg_ctl so that it redirects
> the postmaster's stdout/stderr when a -l switch is given (actually,
> I thought it did that already...).  I do object to changing the logger's
> behavior as you suggest, because that will break use-cases that work
> today.  One that I've used personally is adding "fprintf(stderr)" calls
> in the logger for debugging the logger itself.

The weird thing is, when the logger process dies and is restarted by the
postmaster, then both stdout and stderr point to /dev/null.  So the
behavior is inconsistent either way.

pgsql-bugs by date:

Previous
From: Mayank Mittal
Date:
Subject: Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
Next
From: Tom Lane
Date:
Subject: Re: BUG #7559: syslogger doesn't close stdout and stderr