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

Sergei Kornilov <sk@zsrv.org>

From: Sergei Kornilov <sk@zsrv.org>

To: David Pereiro Lagares <david@nlpgo.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>

Date: 2018-01-17T19:26:15Z

Lists: pgsql-bugs, pgsql-hackers

Hello
I can reproduce on actual 9.6.6, 10.1 and fresh master build (9c7d06d60680c7f00d931233873dee81fdb311c6 commit). I did not check 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

Commits

Improve stability of recently-added regression test case.
- afb5fb290e90 10.6 landed
- 6d2c760b059e 11.1 landed
- 4f6a77e46af2 9.5.15 landed
- 3e406417b8da 9.6.11 landed
- 17d6a8fb764c 12.0 landed
Fix IOS planning when only some index columns can return an attribute.
- be55bfc9386d 9.5.13 landed
- b5febc1d125c 11.0 landed
- 3f26be83ec1e 9.6.9 landed
- 147b59971eba 10.4 landed
Ability to advance replication slots
- 9c7d06d60680 11.0 cited
Allow no-op GiST support functions to be omitted.
- d3a4f89d8a3e 11.0 cited