You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reduce the number of places that hardcode a btree strategy number by
instead using comparison types.
Generalize predicate tests beyond btree strategies. Extend routines
which prove logical implications between predicate expressions to be
usable by more than just B-tree index strategies.
Allow non-btree indexes to participate in mergejoin. Rather than
hardcoding a requirement that the index be of type btree, just require
that it provide ordering support.
A number of places in the code still had references to btree
strategies where not appropriate, so fix those. Leave untouched such
strategy numbers in nbtree, spgist, and brin indexes, and also in
table partitioning. Hardcoded hash and btree references in table
partitioning are part of the design of table partitioning; their
replacement, if even a good idea, is beyond the scope of this patch
series.
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
0 commit comments