Re: BUG #6530: intarray documentation could do with a warning about operators
От | Tom Lane |
---|---|
Тема | Re: BUG #6530: intarray documentation could do with a warning about operators |
Дата | |
Msg-id | 8741.1333988189@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #6530: intarray documentation could do with a warning about operators (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: BUG #6530: intarray documentation could do with a warning
about operators
|
Список | 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 по дате отправления: