Hi, On 2022-08-08 12:19:22 -0400, Tom Lane wrote: > Andres Freund <and...@anarazel.de> writes: > > On 2022-08-08 10:32:22 -0400, Tom Lane wrote: > >> Another idea is that some of the write() calls are failing --- elog.c > >> doesn't check for that. > > > I was suspicious of those as well. It might be a good idea to at least write > > such failures to stderr, otherwise it's just about impossible to debug. Not > > that stderr will always point anywhere useful... > > Uh ... what we are talking about is a failure to write to stderr. > It's not likely that adding more output will help.
I forgot that we don't preserve the original stderr in some other fd, likely because the logger itself still has it open and can use write_stderr(). Greetings, Andres Freund
