From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: elog.c logic bug? |
Date: | 2007-06-06 18:27:29 |
Message-ID: | 4666FC91.303@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> If not I have missed something - why would the syslogger be trying to
>> write to its output (possibly for the second time) regardless of what
>> Log_destination is set to?
>>
>
> You're mistaken: within the syslogger process, stderr doesn't point to
> the same place as the target file (it's normally the same as the
> original postmaster stderr). The reason the code is set up to try to
> write both stderr and the target file is to maximize the chance that an
> internally generated error in syslogger will get reported *someplace*.
>
>
>
OK, thanks, I'll try to make that a bit clearer in a comment.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Hannes Eder | 2007-06-06 19:12:53 | Re: msvc, build and install with cygwin in the PATH |
Previous Message | Greg Smith | 2007-06-06 18:26:11 | Re: Controlling Load Distributed Checkpoints |