Set amcancrosscompare to true for hash

This was missed in the refactoring in patch ce62f2f2a0a, which thus
created a regression.

Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Mark Dilger <mark.dilger@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/flat/E1tngY6-0000UL-2n%40gemulon.postgresql.org

diff --git a/src/backend/access/hash/hash.c b/src/backend/access/hash/hash.c
index a22845d70680210a02850bd80ed8c60ec6d1b25a..4c83b09eddea7cf05c1f94ddf6fb1f15e76f1796 100644 (file)
--- a/src/backend/access/hash/hash.c
+++ b/src/backend/access/hash/hash.c
@@ -65,7 +65,7 @@ hashhandler(PG_FUNCTION_ARGS)
    amroutine->amcanorder = false;
    amroutine->amcanorderbyop = false;
    amroutine->amcanhash = true;
-   amroutine->amcancrosscompare = false;
+   amroutine->amcancrosscompare = true;
    amroutine->amcanbackward = true;
    amroutine->amcanunique = false;
    amroutine->amcanmulticol = false;