From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>,Eugen Konkov <kes-kes(at)yandex(dot)ru>,PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Proposition to use '==' as synonym for 'IS NOT DISTINCT FROM' |
Date: | 2019-10-26 23:21:47 |
Message-ID: | 4E861360-B0C2-4AFC-B102-6C7674308FC9@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On October 26, 2019 4:09:29 PM PDT, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> wrote:
>On 26/10/2019 17:41, Eugen Konkov wrote:
>> Hi.
>>
>> I have noticed that it would be cool to use '==' in place of 'IS
>NOT
>> DISTICT FROM'
>>
>> What do you think about this crazy idea?
>
>
>I think this is a terrible idea. The only reason to do this would be
>to
>index it, but indexes (btree at least) expect STRICT operators, which
>this would not be.
It sounds like what's being suggested is just some abbreviated formulation of IS NOT DISTINCT. If implement that way, rather than manually adding non strict operators, I don't think there would be an indexing issue.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-10-27 01:02:46 | Re: Proposal: Add more compile-time asserts to expose inconsistencies. |
Previous Message | Vik Fearing | 2019-10-26 23:09:29 | Re: Proposition to use '==' as synonym for 'IS NOT DISTINCT FROM' |