BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: elprans(at)gmail(dot)com
Subject: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink
Date: 2022-01-11 22:46:02
Message-ID: 17363-f6d42fd0d726be02@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17363
Logged by: Elvis Pranskevichus
Email address: elprans(at)gmail(dot)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)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2022-01-12 00:48:06 Re: BUG #17361: Unique index constraint inconsistence
Previous Message Peter Geoghegan 2022-01-11 22:19:38 Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7