Re: pgsql: Allow GIN's extractQuery method to signal that nothing can

Поиск
Список
Период
Сортировка
От Teodor Sigaev
Тема Re: pgsql: Allow GIN's extractQuery method to signal that nothing can
Дата
Msg-id 45C0C803.6010504@sigaev.ru
обсуждение исходный текст
Ответ на Re: pgsql: Allow GIN's extractQuery method to signal that nothing can  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
Дерево обсуждения 
> If you're going to support operators that could allow every tuple to

Right now it's a 'contains', 'contained by' operations for arrays.

> match, then I think you had better find a way to allow a full index scan
> within GIN.  Because the above does not fix the problem, it's only a
> very crude band-aid; you *cannot* assume that you'll always have Consts
> to look at.

Ok, I'll remove that.

--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Allow GIN's extractQuery method to signal that nothing can
Следующее
От: teodor@postgresql.org (Teodor Sigaev)
Дата:
Сообщение: pgsql: Revert gincostestimate changes.