Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: feichanghong <feichanghong(at)qq(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit
Date: 2024-01-23 01:15:27
Message-ID: Za8TLyD9HIjzFlhJ@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jan 23, 2024 at 08:38:09AM +0900, Michael Paquier wrote:
> And INJECTION_POINT_1ARG() would be just a wrapper around something
> like:
> extern void InjectionPointRun1(const char *name, void *arg1);
>
> And then plug in the callback you want. Having the callback in a new
> test module with the SQL test itself would be OK, or you could just
> add it to src/test/modules/injection_points/ with a SQL test in it, or
> just use EXTRA_INSTALL.

That would mean to extend the code like the attached, I think. Would
that be useful for you?
--
Michael

Attachment Content-Type Size
0001-Add-support-for-runtime-checks-in-injection-points.patch text/x-diff 14.2 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2024-01-23 03:19:57 Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
Previous Message jian he 2024-01-23 00:00:00 Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum