Re: write_pipe_chunks patch messes up early error message output

From: "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: write_pipe_chunks patch messes up early error message output
Date: 2007-07-16 13:53:06
Message-ID: E1539E0ED7043848906A8FF995BDA579023665AB@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-07-16 14:21:26 Re: write_pipe_chunks patch messes up early error message output
Previous Message Tom Lane 2007-07-16 13:46:58 Re: write_pipe_chunks patch messes up early error message output