| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
| Date: | 2021-05-07 04:42:46 |
| Message-ID: | CA+hUKG+52Td3PevOAqWyT-CcDRgXpgQ-V5PDeS5Rs0HSmrPWOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 7, 2021 at 1:43 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The interesting part of this is frame 6, which points here:
>
> case SYNC_METHOD_FDATASYNC:
> if (pg_fdatasync(fd) != 0)
> ereport(PANIC,
> (errcode_for_file_access(),
> errmsg("could not fdatasync file \"%s\": %m",
> XLogFileNameP(ThisTimeLineID, segno))));
Oh, and I see that 13 has 9989d37d "Remove XLogFileNameP() from the
tree" to fix this exact problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-05-07 04:53:34 | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
| Previous Message | Andres Freund | 2021-05-07 04:38:33 | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |