Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions

From: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
To: Salma Elsayed <salmasayed182003(at)gmail(dot)com>
Cc: pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions
Date: 2026-10-29 17:55:48
Message-ID: CAM527d-N_0+3c61f0sZH06LEk4mupUP_+a18TtMOprriaq6P+Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 28, 2026 at 15:23 UTC, Salma Elsayed
<salmasayed182003(at)gmail(dot)com> wrote:
> This is v4 of the B-tree leaf page merge patch series (3 patches
> attached), rebased on current master. There are a lot of changes since
> v3 [1].

Thanks, Salma. My AI harness for PG hacking found a test issue in the
posted v4: 007 passed 16 of 21 checks when TESTDATADIR contains a space;
five checks get empty pg_waldump output. Could you check how
waldump_range() invokes pg_waldump and handles failures? With a test-only
correction, all 21 checks passed, without a server change.

Targeted reruns for #103, #104 and #105, and adapted reproducers for
#121 and #122, passed in the tested scenarios; 008 passed 703/703.
The exact setup, results and limits are here:
https://github.com/NikolayS/postgres/issues/101#issuecomment-6489250891

#110 and the reported backward parallel deadlock remain open. I have
not reproduced the latter, nor reviewed these results by hand.

Nik

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Burd, Greg 2026-10-29 18:11:29 Re: Return pg_control from pg_backup_stop().
Previous Message Bharath Rupireddy 2026-10-29 17:47:26 Re: Parallel vacuum: workers together with leader could overrun cost budget