Re: index prefetching - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: index prefetching
Date
Msg-id CAH2-WzmpQV7wqbwE_bW+1Ja32chnh87i=wx2Y6NkhFiuEVsBzw@mail.gmail.com
Whole thread
In response to Re: index prefetching  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Sat, Jul 11, 2026 at 1:08 PM Peter Geoghegan <pg@bowt.ie> wrote:
> On Wed, Jul 8, 2026 at 6:14 PM Tomas Vondra <tomas@vondra.me> wrote:
> > I took a quick look on 0001 today, because AFAIK you're intending
> > pushing it in not too distant future. I'll take a look at the other
> > parts too, but I wanted to post the 0001 feedback now.
>
> That's right. I will push 0001 in the next 7-10 days, barring any objections.

I ran out of time to commit the first patch today. Perhaps I will get
to it over the weekend. If not, it'll be at least another week or so,
since I have a work trip all throughout next week.

Attached is V31, which is intended only to fix bit rot against the
master branch. There are some small differences, but they are hardly
worth mentioning.

The only thing that's slightly interesting about V31 is that the
"Limit get_actual_variable_range leaf page reads" patch appears
earlier now (as 0002-*). I plan to make that one into a standalone
patch, with its own CF entry, once 0001 is merged. I'll then discuss
it on a dedicated thread (and stop including it in future revisions of
the index prefetching patch set).

--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: pg_plan_advice: fix parsing underscore in numbers
Next
From: Andres Freund
Date:
Subject: Re: Possible Visibility Map corruption in supported branches?