Re: Re: logical changeset generation v3 - comparison to Postgres-R change set format - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: logical changeset generation v3 - comparison to Postgres-R change set format
Date
Msg-id 12656.1358099084@sss.pgh.pa.us
Whole thread Raw
In response to Re: logical changeset generation v3 - comparison to Postgres-R change set format  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: logical changeset generation v3 - comparison to Postgres-R change set format
List pgsql-hackers
Hannu Krosing <hannu@2ndQuadrant.com> writes:
> How do people feel about adding a real sameness operator ?

Just begs the question of "what's sameness?"

In many places we consider a datatype's default btree equality operator
to define sameness, but not all types provide a btree opclass (in
particular, anything that hasn't got a sensible one-dimensional sort
order will not).  And some do but it doesn't represent anything that
anyone would want to consider "sameness" --- IIRC, some of the geometric
types provide btree opclasses that sort by area.  Even for apparently
simple types like float8 there are interesting questions like whether
minus zero is the same as plus zero.

The messiness here is not just due to lack of a notation.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: enhanced error fields
Next
From: Andres Freund
Date:
Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)