public inbox for [email protected]  

help / color / mirror / Atom feed
From: Peter Geoghegan <[email protected]>
To: Andres Freund <[email protected]>
Cc: Tomas Vondra <[email protected]>
Cc: Alexandre Felipe <[email protected]>
Cc: Thomas Munro <[email protected]>
Cc: Nazir Bilal Yavuz <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Melanie Plageman <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Georgios <[email protected]>
Cc: Konstantin Knizhnik <[email protected]>
Cc: Dilip Kumar <[email protected]>
Subject: Re: index prefetching
Date: Wed, 18 Feb 2026 00:02:34 -0500
Message-ID: <CAH2-Wz=Ag3hrX-YWQAh1NYcvV5ZUzuenVnuZ-+4w55GL6hwpAQ@mail.gmail.com> (raw)
In-Reply-To: <CAH2-Wz=sO3sjqR05t32HkMZ+-iWrZhrNTYE7sg7sxsJBbB2Dpw@mail.gmail.com>
References: <CAE8JnxN_EwnTLLMWGhvgwaomYZ0ysm7NeogA-BqBd=Rs3S7Oqw@mail.gmail.com>
	<64a2re223ajj4popowsyu4xekbuvvyfwkrihn5yzyrkwsmsuvp@2lls3tpww5dl>
	<a67mvhyi2q45eg4eimhpwdg6l3s3dmpahti2svffvmvzwmss27@r4nohusvndbq>
	<[email protected]>
	<il7jtfowpatrlg33qb5plj7v7pferes4ogerq5fdczszi4kokh@sbwvb2ukfgos>
	<[email protected]>
	<ws47e3wly6skt36b23zy5qfvcxzueo6od3uicunuodsqnxl7os@7v2qi7qkxzbz>
	<CAH2-Wzk-89uCvdJ1Q6NsM6LvDvUEt6Qy66T6A60J=D_voWxZDg@mail.gmail.com>
	<64mfcfv7iihc4pmqlxarii4esnmqry52ckz5m7lmwylnfnuxuz@oxh4ioxkjtep>
	<CAH2-Wz=GQaLKy3qaq1iYuKZOKt_2YVx13_wxcTf+xcLMEO4qyg@mail.gmail.com>
	<ttuirsz636fr227k7bfbsuqnmpxknvq2hw6yeg56xb45txjxkd@kvubmvhrd32a>
	<CAH2-Wz=sO3sjqR05t32HkMZ+-iWrZhrNTYE7sg7sxsJBbB2Dpw@mail.gmail.com>

On Tue, Feb 17, 2026 at 8:11 PM Peter Geoghegan <[email protected]> wrote:
> FWIW, the version of the patch you're using is slightly different to
> the one I have here. Since I worked on unrelated issues with things
> like the cost of rescans with nestloop joins. Another difference is
> that the memory allocation for the VM cache is now combined with the
> main batch alloc, which seems to be more cache efficient. And saves us
> memory for plain index scans.

Here's a rebased branch with all of those mostly-unrelated optimization:

https://github.com/petergeoghegan/postgres/tree/index-prefetch-master-vmcache-rescan-optimizations

I suggest that you work off of this, on the off chance that these new
optimizations end up mattering. Which is quite possible with anything
that involves an index-only scan.

-- 
Peter Geoghegan






view thread (11+ 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], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: index prefetching
  In-Reply-To: <CAH2-Wz=Ag3hrX-YWQAh1NYcvV5ZUzuenVnuZ-+4w55GL6hwpAQ@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