Re: index prefetching - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: index prefetching
Date
Msg-id CAH2-WzmR--gW+FrO5z7Uis6GEN84Bh3z_QVbK+QXKXnCYkz3aw@mail.gmail.com
Whole thread
In response to Re: index prefetching  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: index prefetching
Re: index prefetching
List pgsql-hackers
On Mon, Sep 14, 2026 at 2:08 PM Peter Geoghegan <pg@bowt.ie> wrote:
> Attached is v35, which addresses my outstanding concerns about include
> dependencies. Some changes in v35 are similar to ones you
> independently proposed. Even still, thanks for the review.
>
> I will commit 0001 later this week. That kept getting held up by small
> issues, but I finally think I've fixed all of them.

I finally committed the "Add slot-based table AM index scan interface"
work. I also committed Tomas' fix for the pending_read_nblocks read
stream bug that appeared as part of v35.

Attached is v36, which is just to keep the patch series applying.

This version also lacks the "Add get_actual_variable_range index page
read limit" patch carried by previous versions, which I have not
committed. It no longer makes sense to treat that patch as part of
this project, even though it started out that way. It has independent
goals, and no longer relies on any patch carried in this series. So
there's a separate CF entry/thread for it now [1].

[1] https://commitfest.postgresql.org/patch/7305/

--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Return pg_control from pg_backup_stop().
Next
From: surya poondla
Date:
Subject: Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon