Re: Hashable custom types

From: Paul Ramsey <pramsey(at)cleverelephant(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>
Subject: Re: Hashable custom types
Date: 2015-07-08 20:33:50
Message-ID: etPan.559d8931.431bd7b7.e975@Crane.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> It still says I lack the secret sauce...

> ERROR: could not implement recursive UNION
> DETAIL: All column datatypes must be hashable.

UNION will preferentially glom onto the btree equality operator, if memory
serves. If that isn't also the hash equality operator, things won't work
pleasantly.

So… what does that mean for types that have both btree and hash equality operators? Don’t all the built-ins also have this problem? 

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-07-08 20:36:48 Re: Hashable custom types
Previous Message Tom Lane 2015-07-08 20:31:42 Re: Hashable custom types