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

From Sergei Kornilov
Subject Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
Date
Msg-id 412861516217175@web38o.yandex.ru
Whole thread Raw
In response to Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column.  (David Pereiro Lagares <david@nlpgo.com>)
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
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 by date:

Previous
From: Ratnakar Tripathy
Date:
Subject: Re: BUG #14947: Installation Errors
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #15001: planner cann't distinguish composite index?