| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
| Date: | 2021-05-08 02:08:39 |
| Message-ID: | 20210508020839.mq7tojs52jucgja7@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-05-07 17:14:18 -0700, Noah Misch wrote:
> Having a flaky buildfarm member is bad news. I'll LD_PRELOAD the attached to
> prevent fsync from reaching the kernel. Hopefully, that will make the
> hardware-or-kernel trouble unreachable. (Changing 008_fsm_truncation.pl
> wouldn't avoid this, because fsync=off doesn't affect syncs outside the
> backend.)
Not sure how reliable that is - there's other paths that could return an
error, I think. If the root cause is the disk responding weirdly to
write cache flushes, you could tell the kernel that that the disk has no
write cache (e.g. echo write through > /sys/block/sda/queue/write_cache).
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-05-08 02:18:14 | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
| Previous Message | David Rowley | 2021-05-08 02:04:24 | Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays |