Re: Fixing GIN for empty/null/full-scan cases

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Fixing GIN for empty/null/full-scan cases
Дата
Msg-id 4049.1294445970@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Fixing GIN for empty/null/full-scan cases  (David E. Wheeler <david@kineticode.com>)
Ответы Re: Fixing GIN for empty/null/full-scan cases  ("David E. Wheeler" <david@kineticode.com>)
Список pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> We (PGX) actually have a client who could use this. Tom, if you have patches as you work on this (or, better, a
branchin a Git repo), I could do some testing on your client's code with it. It would involve converting from a GiST to
aGIN index and then seeing how well the queries fare. Would that be helpful to you?
 

Well, actually, I just committed it.  If you want to test, feel free.
Note that right now only the anyarray && <@ @> operators are genuinely
fixed ... I plan to hack on tsearch and contrib pretty soon though.
        regards, tom lane


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

Предыдущее
От: David E. Wheeler
Дата:
Сообщение: Re: Fixing GIN for empty/null/full-scan cases
Следующее
От: Tom Lane
Дата:
Сообщение: Remove pg_am.amindexnulls?