BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink
Date
Msg-id 17363-f6d42fd0d726be02@postgresql.org
Whole thread Raw
Responses Re: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17363
Logged by:          Elvis Pranskevichus
Email address:      elprans@gmail.com
PostgreSQL version: 14.0
Operating system:   Linux
Description:

The following fails in PostgreSQL 14:

    postgres14=# SELECT ROW(ROW(ROW(1))) = ANY (SELECT
(ROW(ROW(ROW(1)))).*);
    ERROR:  could not identify a hash function for type record

whereas PostgreSQL 13 works fine:

    postgres13=# SELECT ROW(ROW(ROW(1))) = ANY (SELECT
(ROW(ROW(ROW(1)))).*);  
     ?column?
    ──────────
     t
    (1 row)

Interestingly, reducing the nesting level to two works in 14:

    postgres14=# SELECT ROW(ROW(1)) = ANY (SELECT (ROW(ROW(1))).*);
     ?column?
    ──────────
     t
    (1 row)


pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #17361: Unique index constraint inconsistence