Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT
Date
Msg-id CAH2-Wz=J2d3TFJ1QLTia5Hr-kJXk+URBT8h10vGi6hO82L3kjw@mail.gmail.com
Whole thread
In response to Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Tue, Jun 23, 2026 at 4:06 PM Peter Geoghegan <pg@bowt.ie> wrote:
> Importantly, this allows VISITED_PAGES_LIMIT to work exactly the same
> way on standbys as it does today. During hot standby, LP_DEAD bits
> cannot be set or used to avoid heap fetches. As long as each leaf page
> returns at least one match (which could still be a TID pointing to a
> dead heap tuple), nothing changes -- INDEX_PAGES_LIMIT does nothing
> new, we rely on VISITED_PAGES_LIMIT in the traditional way.

I attach this patch here, to be tracked as its own CF entry going forward.

I committed "Add slot-based table AM index scan interface" this
morning, which this INDEX_PAGES_LIMIT patch depends on. There's no
longer any reason to tie this patch to the index
prefetching/amgetbatch work.

--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT
Next
From: Kyle Snavely
Date:
Subject: Re: {heap,minimal}_expand_tuple() are unused