Re: BUG #17158: Distinct ROW fails with Postgres 14

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.