Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit

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

Dear&nbsp;hlinnaka,

I once attempted to construct a scenario with multiple backends concurrently
performing the split that leads to gin index corruption. Unfortunately, I did
not succeed. The reason is that ginInsertCleanup requires an Exclusive Lock
on METAPAGE, preventing multiple processes from simultaneously executing the
cleanup.&nbsp;

Maybe I missed something. hlinnaka, do you have any suggestions?

Best Regards,
Fei Changhong
Alibaba Cloud Computing Ltd.

&nbsp;

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message feichanghong 2024-03-27 06:53:55 Re: ReplicationSlotRelease may set the statusFlags of other processes in PG14
Previous Message Sandeep Thakkar 2024-03-27 02:59:25 Re: BUG #18395: Checksum verification failed for: deb_postgis_3_4_pg16.app.zip