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

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: David Pereiro Lagares <david(at)nlpgo(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
Date: 2018-01-17 19:26:15
Message-ID: 412861516217175@web38o.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2018-01-17 20:19:50 Re: PostgreSQL crashes with SIGSEGV
Previous Message Tom Lane 2018-01-17 19:23:18 Re: PostgreSQL crashes with SIGSEGV

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-17 19:29:05 Re: [HACKERS] PATCH: enabling parallel execution for cursors explicitly (experimental)
Previous Message Tom Lane 2018-01-17 19:23:18 Re: PostgreSQL crashes with SIGSEGV