pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: elprans@gmail.com
Subject: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink
Date: Tue, 11 Jan 2022 22:46:02 +0000
Message-ID: <17363-f6d42fd0d726be02@postgresql.org> (raw)

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)



view thread (3+ messages)  latest in thread

Message-ID: <17363-f6d42fd0d726be02@postgresql.org>
Permalink:  ../17363-f6d42fd0d726be02@postgresql.org/
Also on:    postgresql.org/message-id/17363-f6d42fd0d726be02@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, elprans@gmail.com
  Subject: Re: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink
  In-Reply-To: <17363-f6d42fd0d726be02@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox