From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: David Rowley <dgrowleyml@gmail.com>
To: sait.nisanci@microsoft.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
Date: Tue, 24 Aug 2021 23:25:09 +0200
Message-ID: <bc0ec85a-68cf-1b99-e80c-ee0c55b936db@enterprisedb.com> (raw)
In-Reply-To: <CAApHDvp0w_5YY=7pxPkymtv7Oc0cGS=+jtiBvXrfcM6gLjT5Pg@mail.gmail.com>
References: <17158-8a2ba823982537a4@postgresql.org>
<CAApHDvp0w_5YY=7pxPkymtv7Oc0cGS=+jtiBvXrfcM6gLjT5Pg@mail.gmail.com>
On 24.08.21 11:55, David Rowley wrote:
> If it's going to be a problem detecting the lack of hashability during
> planning then maybe we can just add a hash opclass for BIT to fix this
> particular case.
The following types have btree opclasses but not hash opclasses:
money
bit
bit varying
tsvector
tsquery
Also among contrib:
cube
ltree
seg
We could fix the first three relatively easily (although money is used
in test cases as not having a hash opclass). Not sure what to do about
the rest.
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: peter.eisentraut@enterprisedb.com, dgrowleyml@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
In-Reply-To: <bc0ec85a-68cf-1b99-e80c-ee0c55b936db@enterprisedb.com>
* 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