Re: Anti-critical-section assertion failure in mcxt.c reached by walsender - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
Date
Msg-id CA+hUKG+52Td3PevOAqWyT-CcDRgXpgQ-V5PDeS5Rs0HSmrPWOA@mail.gmail.com
Whole thread Raw
In response to Re: Anti-critical-section assertion failure in mcxt.c reached by walsender  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
List pgsql-hackers
On Fri, May 7, 2021 at 1:43 PM Tom Lane <tgl@sss.pgh.pa.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.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
Next
From: Tom Lane
Date:
Subject: Re: Anti-critical-section assertion failure in mcxt.c reached by walsender