Re: Adding skip scan (including MDAM style range skip scan) to nbtree - Mailing list pgsql-hackers

From Alena Rybakina
Subject Re: Adding skip scan (including MDAM style range skip scan) to nbtree
Date
Msg-id 3eab6874-6a68-424b-89dd-44320b7e7858@postgrespro.ru
Whole thread Raw
In response to Re: Adding skip scan (including MDAM style range skip scan) to nbtree  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
List pgsql-hackers
On 01.04.2025 17:39, Matthias van de Meent wrote:
On Fri, 28 Mar 2025 at 22:59, Peter Geoghegan <pg@bowt.ie> wrote:
On Tue, Mar 25, 2025 at 7:45 PM Peter Geoghegan <pg@bowt.ie> wrote:
Attached is v31, which has a much-improved _bt_skip_ikeyprefix (which
I've once again renamed, this time to _bt_set_startikey).
Attached is v32
+static bool _bt_s**parray_shrink
I'd like to understand the "shrink" here, as it's not entirely clear to me.
The functions are exclusively called through dispatch in
_bt_compare_array_scankey_args, and I'd expected that naming to be
extended to these functions.
I understood _bt_skiparray_shrink() as the function that refines the range of values that a skip array will consider,
by interpreting existing scalar inequality conditions and applying them to limit the bounds of the skip scan.
I understood "shrink" to mean narrowing the range of values that the skip array will consider during the index scan.
-- 
Regards,
Alena Rybakina
Postgres Professional

pgsql-hackers by date:

Previous
From: Rafael Thofehrn Castro
Date:
Subject: Re: Proposal: Progressive explain
Next
From: Fujii Masao
Date:
Subject: Re: Extend ALTER DEFAULT PRIVILEGES for large objects