Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column. - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.
Date
Msg-id 20180118082505.GA84508@paquier.xyz
Whole thread Raw
In response to Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses 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.
List pgsql-bugs
On Thu, Jan 18, 2018 at 12:57:38PM +0500, Andrey Borodin wrote:
>> 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 only scan 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.

The proposed patch has no regression tests. If the current set is not
enough to stress the problem, you surely should add some (haven't
checked the patch in detail, sorry ;p ).
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column.