Re: [WiP] B-tree page merge during vacuum to reduce index bloat

From: Madhav Madhusoodanan <madhavmadhusoodanan(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Kirk Wolak <wolakk(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Subject: Re: [WiP] B-tree page merge during vacuum to reduce index bloat
Date: 2026-02-28 08:42:16
Message-ID: CAKw2Pb3i2QBuUVAHk=Ao7G0FKvDFGbMAZCZLLcBNQpM5xHPN+A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 27, 2026 at 4:28 PM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
>
> Hi Madhav!
>
> It's available here [0], it's only a prototype.
> But the approach with AccessExclusiveLock is not practically useful.
> Just REINDEX INDEX CONCURRENTLY will do better in most cases.

Thank you for sharing this, Andrey!

> Perhaps, I agree with Pavlo that it seems overly rigorous for GSoC.
> It's more like math research than code typing.

That is a fair point. I do understand that this is going to be more
mathematical, which is why I'd love to help make progress if
mentorship is possible.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-02-28 09:22:03 Re: Fix bug in multixact Oldest*MXactId initialization and access
Previous Message Zhijie Hou (Fujitsu) 2026-02-28 08:40:31 RE: [PATCH] Support automatic sequence replication