Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.
| От | Andrey Borodin |
|---|---|
| Тема | Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column. |
| Дата | |
| Msg-id | 62C2B9A0-51BC-40FF-9BCA-F203784CB9C1@yandex-team.ru обсуждение исходный текст |
| Ответ на | 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 a compositeGIST index with a gist_trgm_ops column.
Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column. Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column. Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column. |
| Список | pgsql-bugs |
Hello! > 18 янв. 2018 г., в 10:48, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> написал(а): > > Gist imposes the ninth strategy to perform index only scan but > planner is not considering that > .... > Please find the attached patch. I agree with you that current behavior is a bug and your patch seems correct. I'm a bit worried about ninth strategy words: fetch is not necessary now, if opclass lacks compress methods - index onlyscan is possible. See https://github.com/postgres/postgres/commit/d3a4f89d8a3e500bd7c0b7a8a8a5ce1b47859128 for details. Though there are tests in cube and seg for that, if your patch passes check-world, than this behavior is not affected. Thank you for the patch! Best regards, Andrey Borodin.
В списке pgsql-bugs по дате отправления: