Re: BUG #6530: intarray documentation could do with a warning about operators

yes, I could not figure out why my GIN index was not used, this is what
i meant.

On 09/04/12 18:16, Tom Lane wrote:
> Robert Haas<robertmhaas(at)gmail(dot)com> writes:
>> We do have this:
>> <para>
>> The operators<literal>&amp;&amp;</>,<literal>@&gt;</> and
>> <literal>&lt;@</> 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

--
Kasper Sandberg
Sandberg Enterprises
+45 51944242
http://www.sandbergenterprises.dk