Message-ID: <a0a6a902cdf1112e73c29df0d31458becfbf793d.camel@cybertec.at>
Subject: Re: pgsql: Handle equality operator in contrib/pg_trgm
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Alexander Korotkov <akorotkov@postgresql.org>,
	pgsql-committers@lists.postgresql.org
Date: Fri, 20 Sep 2024 22:19:26 +0200
In-Reply-To: <E1keAyM-0000qd-Dy@gemulon.postgresql.org>
References: <E1keAyM-0000qd-Dy@gemulon.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-1.fc40) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/a0a6a902cdf1112e73c29df0d31458becfbf793d.camel%40cybertec.at>
Precedence: bulk

On Sun, 2020-11-15 at 05:53 +0000, Alexander Korotkov wrote:
> Handle equality operator in contrib/pg_trgm
>=20
> Obviously, in order to equality operator be satisfiable, target string mu=
st
> contain all the trigrams of the search string.=C2=A0 On this base, we imp=
lement
> equality operator in GiST/GIN indexes with recheck.
>=20
> Discussion: https://postgr.es/m/CAOBaU_YWwtT7tdggtROacjdOdeYHCz-tmSwuC-j-=
TOG-g97J0w%40mail.gmail.com
> Author: Julien Rouhaud
> Reviewed-by: Tom Lane, Alexander Korotkov, Georgios Kokolatos, Erik Rijke=
rs
>=20
> Branch
> ------
> master
>=20
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/935f6666502250abde8615bc7805a6e5=
aa05a066

This causes bad query results with non-deterministic collations, see
https://postgr.es/m/8ef4899c4acfebca45cc6c042a6dc611d25ffab1.camel@cybertec=
.at

Yours,
Laurenz Albe