Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.

Поиск
Список
Период
Сортировка
От Sergei Kornilov
Тема Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
Дата
Msg-id 412861516217175@web38o.yandex.ru
обсуждение исходный текст
Ответ на Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.  (David Pereiro Lagares <david@nlpgo.com>)
Ответы Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Список pgsql-bugs
Hello
I can reproduce on actual 9.6.6, 10.1 and fresh master build (9c7d06d60680c7f00d931233873dee81fdb311c6 commit). I did
notcheck earlier versions
 

set enable_indexonlyscan to off ;
postgres=# SELECT w FROM words WHERE w LIKE '%e%';
   w   
-------
 Lorem
Index scan result is correct. Affected only index only scan,

PS: i find GIST(w gist_trgm_ops, w); some strange idea, but result is incorrect in any case.

best regards, Sergei


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

Предыдущее
От: Ratnakar Tripathy
Дата:
Сообщение: Re: BUG #14947: Installation Errors
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: BUG #15001: planner cann't distinguish composite index?