| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug on log generation ? |
| Date: | 2022-08-08 16:38:22 |
| Message-ID: | 20220808163822.l4eh6ntev54verjd@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-08-08 12:19:22 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-08-08 16:44:31 | Re: 2022-08-11 release announcement draft |
| Previous Message | Tom Lane | 2022-08-08 16:20:59 | Re: make update-po@master stops at pg_upgrade |