Re: BUG #6530: intarray documentation could do with a warning about operators - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6530: intarray documentation could do with a warning about operators
Date
Msg-id 8741.1333988189@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6530: intarray documentation could do with a warning about operators  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #6530: intarray documentation could do with a warning about operators  (Kasper Sandberg <kontakt@sandberg-consult.dk>)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> We do have this:

>   <para>
>    The operators <literal>&&</>, <literal>@></> and
>    <literal><@</> are equivalent to <productname>PostgreSQL</>'s built-in
>    operators of the same names, except that they work only on integer arrays
>    that do not contain nulls, while the built-in operators work for any array
>    type.  This restriction makes them faster than the built-in operators
>    in many cases.
>   </para>

> But maybe some more explicit warning is needed.  Not sure exactly what.

I think the gripe is basically that, while these operators might be
equivalent to the built-in ones as far as results go, they are not
equivalent in terms of their ability to match to indexes.  But not
sure how we turn that observation into useful documentation.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #6545: le telechargement ne s acheve pas
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support