| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Steve Singer <steve(at)ssinger(dot)info>, 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-24 09:42:21 |
| Message-ID: | 52415E7D.9040807@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/23/2013 10:38 PM, Stephen Frost wrote:
>
>>> and heavily caveated.
>> I'm not sure what caveats would be needed. It seems to me that a
>> clear description of what it does would suffice. Like all the
>> other non-default opclasses in core, it will be non-default because
>> it is less frequently useful.
> "This will claim things are different, even when they aren't different
> when cast to text, or possibly even when extracted in binary mode,
> ensure this is really what you want" is a pretty big caveat, imv.
Yes, it should be documented that it tests for sameness and gives
no guarantees that lack of sameness means "different" (as
determined by some other operator)
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2013-09-24 09:58:25 | Re: ENABLE/DISABLE CONSTRAINT NAME |
| Previous Message | Andres Freund | 2013-09-24 09:14:28 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE - visibility semantics |