Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
To: David Rowley <dgrowleyml@gmail.com>, sait.nisanci@microsoft.com,
 PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
References: <17158-8a2ba823982537a4@postgresql.org>
 <CAApHDvp0w_5YY=7pxPkymtv7Oc0cGS=+jtiBvXrfcM6gLjT5Pg@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Message-ID: <bc0ec85a-68cf-1b99-e80c-ee0c55b936db@enterprisedb.com>
Date: Tue, 24 Aug 2021 23:25:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: 
 <CAApHDvp0w_5YY=7pxPkymtv7Oc0cGS=+jtiBvXrfcM6gLjT5Pg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/bc0ec85a-68cf-1b99-e80c-ee0c55b936db%40enterprisedb.com>
Precedence: bulk

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.