Andres Freund <andres@2ndquadrant.com> wrote:
> I think it's far more realistic to implement an identity operator
> that will fall back to a type specific operator iff equals has
> "strange" properties.
My biggest problem with that approach is that it defaults to
incorrect behavior for types for which user-visible differences
among "equal" values are possible, and requires per-type fixes to
get correct behavior. The approach in this patch provides correct
behavior as the default, with possible per-type changes for
optimization, as people find that desirable.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company