From 56ba0463d38c17400a090353db47cf455ce01c3d Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sat, 1 Mar 2025 09:15:27 +0100 Subject: Set amcancrosscompare to true for hash This was missed in the refactoring in patch ce62f2f2a0a, which thus created a regression. Reported-by: Tom Lane Reviewed-by: Mark Dilger Discussion: https://www.postgresql.org/message-id/flat/E1tngY6-0000UL-2n%40gemulon.postgresql.org --- src/backend/access/hash/hash.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/backend/access/hash/hash.c b/src/backend/access/hash/hash.c index a22845d7068..4c83b09edde 100644 --- 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; -- cgit v1.2.3