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

From Andrey Borodin
Subject Re: [WiP] B-tree page merge during vacuum to reduce index bloat
Date
Msg-id D95C9D6F-62A4-446D-B9A9-EF17FF786351@yandex-team.ru
Whole thread Raw
In response to Re: [WiP] B-tree page merge during vacuum to reduce index bloat  (Madhav Madhusoodanan <madhavmadhusoodanan@gmail.com>)
Responses Re: [WiP] B-tree page merge during vacuum to reduce index bloat
List pgsql-hackers

> On 27 Feb 2026, at 14:54, Madhav Madhusoodanan <madhavmadhusoodanan@gmail.com> wrote:
>
>
> On a related note, I noticed the same topic on the 2026 projects list
> in the Google Summer of Code page. It mentions that a prototype
> extension (pg_btree_compact) has been developed. How do I access the
> same?

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.

We have to develop locking and pining protocols that:
1. Allow both Forward and Backward scans
2. Have indistinguishable locking and pining effect on index
Perhaps, I agree with Pavlo that it seems overly rigorous for GSoC.
It's more like math research than code typing.

Thanks for your interest!


Best regards, Andrey Borodin.

[0] https://github.com/x4m/postgres_g/commit/a5eea2d


pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Portable StaticAssertExpr
Next
From: Amit Kapila
Date:
Subject: Re: [PATCH] Support automatic sequence replication