Message-ID: <cdabb7d6326326388a2914cc4d30cfc6d5969019.camel@cybertec.at>
Subject: Re: BUG #18636: I am seeing a difference in behavior between 13.12
 and 15.6 for full text searching
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: glenncipolla@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Fri, 27 Sep 2024 16:00:08 +0200
In-Reply-To: <18636-3f0e3fe4e7ac0b1c@postgresql.org>
References: <18636-3f0e3fe4e7ac0b1c@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/cdabb7d6326326388a2914cc4d30cfc6d5969019.camel%40cybertec.at>
Precedence: bulk

On Fri, 2024-09-27 at 13:28 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>=20
> Bug reference:      18636
> Logged by:          Glenn Cipolla
> Email address:      glenncipolla@gmail.com
> PostgreSQL version: 13.12
> Operating system:   Ubuntu 11.4
> Description:       =20
>=20
> The following query
>=20
> select to_tsvector('simple','RG147SW RG14 Greenham Road Newbury  West
> Berkshire')
>   @@ to_tsquery('simple', 'gree,west:*');
>=20
> Returns false in PG 15.6, but returns true in pg 13.12.  In 15.6 the code
> returns 'gree:* <-> 'west':*. =20
> In 13.12 it returns 'gree:* & 'west':*
>=20
> This article says the 13.12 behavior was a bug that was fixed in 14.x
> (https://akorotkov.github.io/blog/2021/05/22/pg-14-query-parsing/).
>=20
> I have a dev team about to change their code to handle the new <->.  Befo=
re
> they do that, I would like a confirmation that this functionality is=20
> 1. A bug
> 2. The new functionality will not change back in newer versions.  Do you
> intent to stick with the <-> return value?

We intend to stick with the way it works now... unless somebody comes
up with a very good reason why that behavior is buggy and worth the
compatibility pain the fix incurs.