Support non-btree indexes in get_actual_variable_range()
authorPeter Eisentraut <[email protected]>
Fri, 4 Apr 2025 10:10:28 +0000 (12:10 +0200)
committerPeter Eisentraut <[email protected]>
Fri, 4 Apr 2025 10:21:34 +0000 (12:21 +0200)
commit9ef1851685b718264de47bf543505cf3ec25aaea
treef24bedb0c7e1c74fd6059d9db9d4a860b3a66d5a
parent0d6c4776647feeee26f3e29fff6a5edb222fa260
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 <[email protected]>
Co-authored-by: Peter Eisentraut <[email protected]>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330@enterprisedb.com
src/backend/utils/adt/selfuncs.c