pgsql: Support non-btree indexes in get_actual_variable_range()

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Support non-btree indexes in get_actual_variable_range()
Date: 2025-04-04 10:31:12
Message-ID: E1u0eKO-002c9Q-0v@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Support non-btree indexes in get_actual_variable_range()

This was previously not supported because the btree strategy numbers
were hardcoded. Now we can support this for any index that has the
required strategy mapping support and the required operators.

If an index scan used for get_actual_variable_range() requires
recheck, we now just ignore it instead of erroring out. With btree we
knew this couldn't happen, but now it might.

Author: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Co-authored-by: Peter Eisentraut <peter(at)eisentraut(dot)org>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330(at)enterprisedb(dot)com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9ef1851685b718264de47bf543505cf3ec25aaea

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2025-04-04 10:33:00 pgsql: Allow "COPY table TO" command to copy rows from materialized vie
Previous Message Fujii Masao 2025-04-04 10:04:31 pgsql: Extend ALTER DEFAULT PRIVILEGES to define default privileges for