mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Generalize hash and ordering support in amapi
Stop comparing access method OID values against HASH_AM_OID and BTREE_AM_OID, and instead check the IndexAmRoutine for an index to see if it advertises its ability to perform the necessary ordering, hashing, or cross-type comparing functionality. A field amcanorder already existed, this uses it more widely. Fields amcanhash and amcancrosscompare are added for the other purposes. Author: Mark Dilger <mark.dilger@enterprisedb.com> Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330@enterprisedb.com
This commit is contained in:
@ -103,6 +103,10 @@ typedef struct IndexAmRoutine
|
||||
bool amcanorder;
|
||||
/* does AM support ORDER BY result of an operator on indexed column? */
|
||||
bool amcanorderbyop;
|
||||
/* does AM support hashing using API consistent with the hash AM? */
|
||||
bool amcanhash;
|
||||
/* does AM support cross-type comparisons? */
|
||||
bool amcancrosscompare;
|
||||
/* does AM support backward scanning? */
|
||||
bool amcanbackward;
|
||||
/* does AM support UNIQUE indexes? */
|
||||
|
Reference in New Issue
Block a user