From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: record identical operator |
Date: | 2013-09-17 09:08:28 |
Message-ID: | 52381C0C.6080404@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/16/2013 04:01 PM, Kevin Grittner wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> wrote:
>
>> Lots of people were bitten when (undocumented) hash
>> functions were changed thus breaking hash-based partitioning.
> Nobody can be affected by the new operators in this patch unless
> they choose to use them to compare two records. They don't work
> for any other type and they don't come into play unless you
> specifically request them.
>
Maybe the binary equality operator should be named ====
for "really deeply equal"
to distinguish it from === which would be merely NOT DISTINCT FROM
we could even go one step further and define ===== to mean "the same".
?
This could fit better in conceptual sequence of operator 'strength'
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2013-09-17 09:16:31 | Typo fix in spgtextproc.c |
Previous Message | Rushabh Lathia | 2013-09-17 09:03:04 | Re: insert throw error when year field len > 4 for timestamptz datatype |