Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Heikki Linnakangas <hlinnaka@iki.fi>

Cc: feichanghong <feichanghong@qq.com>, pgsql-bugs <pgsql-bugs@lists.postgresql.org>

Date: 2024-01-23T01:15:27Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix locking when fixing an incomplete split of a GIN internal page
- e6511fe649c5 12.18 landed
- e74c916657b5 13.14 landed
- f120c0872427 14.11 landed
- e43425f48154 15.6 landed
- b899e00e716b 16.2 landed
- 6a1ea02c491d 17.0 landed
Add backend support for injection points
- d86d20f0ba79 17.0 cited

Attachments

0001-Add-support-for-runtime-checks-in-injection-points.patch (text/x-diff) patch 0001

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