Skip site navigation (1) Skip section navigation (2)

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: kenaniah <kenaniah(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6401: IS DISTINCT FROM improperly compares geomoetric datatypes
Date: 2012-01-19 13:30:44
Message-ID: 1326979145-sup-7356@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Excerpts from Heikki Linnakangas's message of jue ene 19 07:25:36 -0300 2012:

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

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2012-01-19 13:40:33
Subject: Re: BUG #6401: IS DISTINCT FROM improperly compares geomoetric datatypes
Previous:From: Heikki LinnakangasDate: 2012-01-19 10:25:36
Subject: Re: BUG #6401: IS DISTINCT FROM improperly compares geomoetric datatypes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group