Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> We do have this:
> 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.
> 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
In response to
pgsql-bugs by date
|Next:||From: Kasper Sandberg||Date: 2012-04-09 16:21:56|
|Subject: Re: BUG #6530: intarray documentation could do with a warning
|Previous:||From: Robert Haas||Date: 2012-04-09 16:15:47|
|Subject: Re: BUG #6545: le telechargement ne s acheve pas|