| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Reinhard Max <reinhard(at)m4x(dot)de>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7559: syslogger doesn't close stdout and stderr |
| Date: | 2012-09-21 17:47:55 |
| Message-ID: | 505CA84B.4090808@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-21 18:17:46 | Re: BUG #7559: syslogger doesn't close stdout and stderr |
| Previous Message | Mayank Mittal | 2012-09-21 11:48:42 | Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes |