Re: BUG #6401: IS DISTINCT FROM improperly compares geomoetric datatypes

Excerpts from Heikki Linnakangas's message of jue ene 19 07:25:36 -0300 201=
2:

> Frankly that's such a rare corner case that I'm not very enthusiastic=20
> about fixing it. One idea would be to look up the type's b-tree sort=20
> operators, and pick the equality operator from there. But point datatype=
=20
> doesn't have b-tree sort operators, either, so it wouldn't help in this=
=20
> case.

It doesn't have a hash opclass either, which could be used as a fallback
in case there's no btree.  Point cannot obviously have a btree opclass
(no inequalities), but a hash one seems possible.

I think the use case of IS NOT DISTINCT FROM for rowtypes in triggers is
a valid one.

--=20
=C3=81lvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support