Re: Restore vacuum_delay_point() in GIN posting-tree leaf vacuum

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Paul Kim <mok03127(at)gmail(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Restore vacuum_delay_point() in GIN posting-tree leaf vacuum
Date: 2026-07-22 19:28:53
Message-ID: CAPpHfdtoMnMPSksdjWx8tsM0RCXSpmYLQGYF+rzbK00Tf-q6HQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 20, 2026 at 10:10 PM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> > On 20 Jul 2026, at 16:59, Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> >
> > We're holding cleanup lock on posting tree root while
> > ginScanPostingTreeToDelete(), not ginVacuumPostingTreeLeaves(). So, I
> > think yes, vacuum_delay_point() was deleted unintentionally.
>
> Yup, my recollection was wrong. ginVacuumPostingTreeLeaves() seems fine for a
> delay point.

Please, check the patch attached.

------
Regards,
Alexander Korotkov
Supabase

Attachment Content-Type Size
v1-0001-Restore-vacuum_delay_point-in-GIN-posting-tree-le.patch application/octet-stream 2.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-07-22 19:55:32 Re: pgsql: Move tar detection and compression logic to common.
Previous Message Andrew Dunstan 2026-07-22 19:28:02 Re: pgsql: Move tar detection and compression logic to common.