| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:19:22 |
| Message-ID: | 634239.1659975562@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Having said that, looping on EAGAIN seems like a reasonably harmless
change. Whether it will help here is really hard to say, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-08 16:20:59 | Re: make update-po@master stops at pg_upgrade |
| Previous Message | Matthias van de Meent | 2022-08-08 16:17:37 | Re: Remaining case where reltuples can become distorted across multiple VACUUM operations |