Re: record identical operator - Review

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Steve Singer <steve(at)ssinger(dot)info>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: record identical operator - Review
Date: 2013-10-07 00:20:51
Message-ID: 20131007002051.GC22450@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 3, 2013 at 10:46:05AM -0700, Kevin Grittner wrote:
> >           opcname
> >     ---------------------
> >     varchar_ops
> >     kd_point_ops
> >     cidr_ops
> >     text_pattern_ops
> >     varchar_pattern_ops
> >     bpchar_pattern_ops
> >     (6 rows)
> >
> > Do these all have operators defined too?
>
> Every operator class is associated with operators.  For example,
> while text_pattern_ops uses the same = and <> operators as the
> default text opclass (because that already uses memcmp), it adds
> ~>~, ~>=~, ~<~, and ~<=~ operators which also use memcmp (ignoring
> character encoding and collation).

OK, my questions have been answered and I am no longer concerned about
this patch causing "equality" confusion for our users.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rushabh Lathia 2013-10-07 04:41:24 Re: insert throw error when year field len > 4 for timestamptz datatype
Previous Message Tomas Vondra 2013-10-06 22:41:58 Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption