@@ -337,19 +337,20 @@ WHERE p1.oprlsortop != p1.oprrsortop AND
337337-- Hashing only works on simple equality operators "type = sametype",
338338-- since the hash itself depends on the bitwise representation of the type.
339339-- Check that allegedly hashable operators look like they might be "=".
340- -- NOTE: in6.5 , this search finds int4eqoid and oideqint4. Until we have
341- -- some cleaner way of dealing with binary-equivalent types, just leave
342- -- thosetwo tuples in the expected output.
340+ -- NOTE: in7.2 , this search finds int4eqoid, oideqint4, and xideqint4.
341+ --Until we have some cleaner way of dealing with binary-equivalent types,
342+ --just leave thosethree tuples in the expected output.
343343SELECT p1.oid, p1.oprname
344344FROM pg_operator AS p1
345345WHERE p1.oprcanhash AND NOT
346346 (p1.oprkind = 'b' AND p1.oprresult = 16 AND p1.oprleft = p1.oprright AND
347347 p1.oprname = '=' AND p1.oprcom = p1.oid);
348348 oid | oprname
349349------+---------
350+ 353 | =
350351 1136 | =
351352 1137 | =
352- (2 rows)
353+ (3 rows)
353354
354355-- In 6.5 we accepted hashable array equality operators when the array element
355356-- type is hashable. However, what we actually need to make hashjoin work on