Home > mailing lists

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	January 24, 2018 03:13:51
Msg-id	348951516742031@web54j.yandex.ru Whole thread Raw
In response to	Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column. (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses	Re: Index-only scan returns incorrect results when using a compositeGIST index with a gist_trgm_ops column. Re: Index-only scan returns incorrect results when using a compositeGIST 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. Re: Index-only scan returns incorrect results when using acomposite GIST index with a gist_trgm_ops column.
List	pgsql-bugs

Tree view

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"
failson 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

pgsql-bugs by date:

From: Tom Lane
Date: 24 January 2018, 02:19:37
Subject: Re: ERROR: could not devise a query plan for the given query (UNIONS and LATERAL)

From: Bruce Momjian
Date: 24 January 2018, 05:23:19
Subject: Re: BUG #14912: Undocumented: 'psql -l' assumes database'postgresql' not $USER

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

Previous

Next