[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] record identical operator - Review
From:       Kevin Grittner <kgrittn () ymail ! com>
Date:       2013-09-30 13:08:12
Message-ID: 1380546492.6460.YahooMailNeo () web162902 ! mail ! bf1 ! yahoo ! com
[Download RAW message or body]

Steve Singer <steve@ssinger.info> wrote:

> How about
>
>   To support matching of rows which include elements without a default
>     B-tree operator class, the following operators are defined for composite
>     type comparison:
>     <literal>*=</>,
>     <literal>*&lt;&gt;</>,
>     <literal>*&lt;</>,
>     <literal>*&lt;=</>,
>     <literal>*&gt;</>, and
>     <literal>*&gt;=</>.
>
> These operators compare the internal binary representation of the two
> rows.  Two rows might have a different binary representation even
> though comparisons of the two rows with the equality operator is true. 
> The ordering of rows under these comparision operators is deterministic
> but not otherwise meaningful.  These operators are used internally for
> materialized views and might be useful for other specialized purposes
> such as replication but are not intended to be generally useful for
> writing queries.

I agree that's an improvement.  Thanks!

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread]