Re: write_pipe_chunks patch messes up early error message output - Mailing list pgsql-hackers

From Tom Lane
Subject Re: write_pipe_chunks patch messes up early error message output
Date
Msg-id 24765.1184688526@sss.pgh.pa.us
Whole thread Raw
In response to Re: write_pipe_chunks patch messes up early error message output  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: write_pipe_chunks patch messes up early error message output
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Or, looking at it another way, why would we ever want the syslogger to 
> use the chunking protocol at all?

Ah, I misunderstood you.  Yeah, I think you are right: if we are
special-casing the syslogger process anyway, then it need only have
these two behaviors:

not redirection_done: write to own stderr (not chunked) and directly to
file

redirection_done: write directly to file

One thing to watch out for is infinite recursion if the write-to-file
gets an error.  I don't remember if we have a defense against that
in there now, but we probably should.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: compiler warnings on the buildfarm
Next
From: Magnus Hagander
Date:
Subject: Re: SSPI authentication