Re: index prefetching

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Georgios <gkokolatos(at)protonmail(dot)com>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Subject: Re: index prefetching
Date: 2025-07-22 13:55:42
Message-ID: f4f348f0-cc4e-463e-a6e5-dfadd6f4be92@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/21/25 14:39, Thomas Munro wrote:
> ...
>
> Here's a sketch of the above two ideas for discussion (.txt to stay
> off cfbot's radar for this thread). Better than save/restore?
>
> Here also are some alternative experimental patches for preserving
> accumulated look-ahead distance better in cases like that. Needs more
> exploration... thoughts/ideas welcome...

Thanks! I'll rerun the tests with these patches once the current round
of tests (with the simple distance restore after a reset) completes.

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2025-07-22 14:01:15 Re: Memory consumed by paths during partitionwise join planning
Previous Message Tomas Vondra 2025-07-22 13:51:12 Re: AIO v2.5