pgsql: Support non-btree indexes in get_actual_variable_range() - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Support non-btree indexes in get_actual_variable_range()
Date
Msg-id E1u0eKO-002c9Q-0v@gemulon.postgresql.org
Whole thread Raw
List 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.dilger@enterprisedb.com>
Co-authored-by: Peter Eisentraut <peter@eisentraut.org>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330@enterprisedb.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(-)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Extend ALTER DEFAULT PRIVILEGES to define default privileges for
Next
From: Fujii Masao
Date:
Subject: pgsql: Allow "COPY table TO" command to copy rows from materialized vie