From: Sergei Kornilov <sk@zsrv.org>
To: David Pereiro Lagares <david@nlpgo.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
Date: Wed, 17 Jan 2018 22:26:15 +0300
Message-ID: <412861516217175@web38o.yandex.ru> (raw)
In-Reply-To: <1516210494.1798.16.camel@nlpgo.com>
References: <1516210494.1798.16.camel@nlpgo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: sk@zsrv.org, david@nlpgo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Index-only scan returns incorrect results when using a composite GIST index with a gist_trgm_ops column.
In-Reply-To: <412861516217175@web38o.yandex.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox