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

From Zeugswetter Andreas ADI SD
Subject Re: write_pipe_chunks patch messes up early error message output
Date
Msg-id E1539E0ED7043848906A8FF995BDA579023665AB@m0143.s-mxs.net
Whole thread Raw
In response to Re: write_pipe_chunks patch messes up early error message output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > Is there any reason we can't just use a check on whether
> SysLoggerPID
> > is not 0?
>
> (a) that really shouldn't be exported out of postmaster.c,
> and (b) it is not readily available to child backends is it?

Should there be child backends when the logger did not start ?
I'd think startup would be aborted if that happed ?

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: write_pipe_chunks patch messes up early error message output
Next
From: Andrew Dunstan
Date:
Subject: Re: write_pipe_chunks patch messes up early error message output