public inbox for [email protected]
help / color / mirror / Atom feedFrom: Madhav Madhusoodanan <[email protected]>
To: Matthias van de Meent <[email protected]>
Cc: Kirk Wolak <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: pgsql-hackers <[email protected]>
Cc: Nikolay Samokhvalov <[email protected]>
Subject: Re: [WiP] B-tree page merge during vacuum to reduce index bloat
Date: Wed, 11 Mar 2026 15:10:22 +0530
Message-ID: <CAKw2Pb2ga_MKhc4HsfiO9xKNcCUv2H=wg3zxMR4=EBPDNWEcfA@mail.gmail.com> (raw)
In-Reply-To: <CAEze2WjL6sXRrT6sSFzaCZUma7GJyOkMkGKXOHT1GuojUScpcQ@mail.gmail.com>
References: <[email protected]>
<CAEze2Wg2a8LQDRocVPa7Df2qXQLrTz-xSu1k3xP3x_6ABVo1Jw@mail.gmail.com>
<CACLU5mRude0L5psEj5WS0DVDv=AHN0McfZBKV5eBoW0JqwwZDA@mail.gmail.com>
<CAKw2Pb2wV=L4yeAqj27wJ1wptHt1mnBaQ5t4YuLLe+M5aU6ESg@mail.gmail.com>
<CAEze2WhPwEAszAOV+3_Oc63V=8JcnsY_4FD3XRLzRi0q0nNdUA@mail.gmail.com>
<CAKw2Pb19rE+sJPpCXhfk8T4K+snfa240_eDXs0dqpCsXoS6cgA@mail.gmail.com>
<CAKw2Pb3=PrcznZuweLLyHt4gmRLyO9cffqRfTm27BFgruGWgWw@mail.gmail.com>
<CAKw2Pb3XJXMPv6zPVwrnTJDZkD+SpUkK61B2hjj+D+KGPWahHA@mail.gmail.com>
<CAEze2WjL6sXRrT6sSFzaCZUma7GJyOkMkGKXOHT1GuojUScpcQ@mail.gmail.com>
On Tue, Mar 10, 2026 at 5:23 PM Matthias van de Meent
<[email protected]> wrote:
>
> They're exclusively for btree code's use; extensions (*) must not add
> to (or change the meaning of) those bits, lest they create a forward
> incompatibility with core PostgreSQL btree code in newer major
> versions; it would cause corrupted binary upgraded databases.
> But patches against core btree code can use those bits, because
> forward compatibility is less of an issue there - we don't really
> support binary upgrades manually patched systems, especially if they
> have incompatible on-disk data.
Noted, I'm looking at it from the core btree code side of things.
I'm unable to see a way where scans or VACUUM calls can recognise
transient merge states if we implement merging as an extension.
Madhav
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [WiP] B-tree page merge during vacuum to reduce index bloat
In-Reply-To: <CAKw2Pb2ga_MKhc4HsfiO9xKNcCUv2H=wg3zxMR4=EBPDNWEcfA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox