Re: contrib/intarray (was Re: Fixing GIN for empty/null/full-scan cases)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: contrib/intarray (was Re: Fixing GIN for empty/null/full-scan cases)
Дата
Msg-id 18540.1294526983@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: contrib/intarray (was Re: Fixing GIN for empty/null/full-scan cases)  ("David E. Wheeler" <david@kineticode.com>)
Список pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Jan 8, 2011, at 1:59 PM, Tom Lane wrote:
>> There seem to be three ways
>> in which intarray is simpler/faster than the generic operators:
>> 
>> * restricted to integer arrays
>> * restricted to 1-D arrays
>> * doesn't allow nulls in the arrays

> My understanding is that they also perform much better if the values in an integer array are ordered. Does that
matter?

Some of the operations sort the array contents as an initial step.  I'm
not sure how much faster they'll be if the array is already ordered,
but in any case they don't *require* presorted input.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: Wildcard search support for pg_trgm
Следующее
От: Jeff Davis
Дата:
Сообщение: Re: WIP: Range Types