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

From Tom Lane
Subject Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
Date
Msg-id 9670.1620363214@sss.pgh.pa.us
Whole thread Raw
In response to Re: Anti-critical-section assertion failure in mcxt.c reached by walsender  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes:
> 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:

> Oh, and I see that 13 has 9989d37d "Remove XLogFileNameP() from the
> tree" to fix this exact problem.

Hah, so that maybe explains why thorntail has only shown this in
the v12 branch.  Should we consider back-patching that?

The more general issue of how to detect, or else make safe,
pallocs in critical error reports remains.  But I bet any answer
we think of for that will not be back-patchable.  So back-patching
a localized fix for the specific bug we know of might be worth doing.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
Next
From: Yugo NAGATA
Date:
Subject: Re: Implementing Incremental View Maintenance