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: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, "michael.paquier@gmail.com" <michael.paquier@gmail.com>
Cc: "x4mmm@yandex-team.ru" <x4mmm@yandex-team.ru>, "david@nlpgo.com" <david@nlpgo.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-01-23T21:13:51Z
Lists: pgsql-bugs, pgsql-hackers
Hello
I tested this patch and think it can be commited to master. Is there a CF record? I can not find one.

Should we also make backport to older versions? I test on REL_10_STABLE - patch builds and works ok, but "make check" fails on new testcase with error:
>  CREATE INDEX ON t USING gist (a test_inet_ops, a inet_ops);
>+ ERROR:  missing support function 4 for attribute 1 of index "t_a_a1_idx"
and with different explain results.

regards, Sergei


Commits

  1. Improve stability of recently-added regression test case.

  2. Fix IOS planning when only some index columns can return an attribute.

  3. Ability to advance replication slots

  4. Allow no-op GiST support functions to be omitted.