Re: Use log_newpage_range in HASH index build - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Use log_newpage_range in HASH index build
Date
Msg-id CA+TgmoZRs3ArQC_rkVCx_Q7rWCM+QF-Q6ERRYUaN4tUvr+rd7w@mail.gmail.com
Whole thread
In response to Re: Use log_newpage_range in HASH index build  (lakshmi <lakshmigcdac@gmail.com>)
Responses Re: Use log_newpage_range in HASH index build
List pgsql-hackers
On Mon, Jan 5, 2026 at 3:48 AM lakshmi <lakshmigcdac@gmail.com> wrote:
> Following up on my earlier note, I implemented the proposed HASH overflow page reuse enhancement.Recently freed
overflowpages are recorded in 
> _hash_freeovflpage( ),and _hash_addovflpage( ) now prefers reusing those pages during allocation before falling back
tothe bitmap scan. 
>
> The change is backend-local and allocation-only,with no WAL or on-disk format changes.I verified correctness using
indexbuild/drop and VACUUM cycles,and confirmed WAL neutrality by comparing WAL generated during HASH index builds with
andwithout this change (no  observable difference beyond normal noise). 
>
> The patch is attached for review.Feedback is welcome.

It is probably best to start a separate email thread specifically
about this patch, because it's doing something quite different from
the original patch. I suggest presenting some specific performance
results, as it's not very clear how much benefit this might have. It
might be good to test a favorable scenario and also an unfavorable
scenario, describing and showing results for each.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Use log_newpage_range in HASH index build
Next
From: Noah Misch
Date:
Subject: Separators in pg_hosts.conf fields