Re: Restore vacuum_delay_point() in GIN posting-tree leaf vacuum - Mailing list pgsql-hackers

On Mon, Jul 20, 2026 at 1:45 PM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> > On 19 Jul 2026, at 19:27, Paul Kim <mok03127@gmail.com> wrote:
> >
> > no CHECK_FOR_INTERRUPTS()
>
> As far as I remember, we hold a cleanup lock on posting tree root.
> We cannot process interrupts while holding a LWLock.
>
> I'm afraid to fix this problem we need a real page deletion with
> full fledged concurrency protocol as we do it in B-tree or GiST.
>
> I've written a patch for this in 2018. I hope to return to this one day.

We're holding cleanup lock on posting tree root while
ginScanPostingTreeToDelete(), not ginVacuumPostingTreeLeaves().  So, I
think yes, vacuum_delay_point() was deleted unintentionally.  I'm
going to get closer look on this in the next couple of days.

------
Regards,
Alexander Korotkov
Supabase