Date: Wed, 16 Oct 2024 12:10:40 +0200 (CEST)
From: bjdev.gthb@laposte.net
Reply-To: bjdev.gthb@laposte.net
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Message-ID: <292395358.3411411.1729073440569@wlpnf0212.sys.meshcore.net>
In-Reply-To: <3737494.1728921663@sss.pgh.pa.us>
References: <18654-c09f568d3ba6dfcd@postgresql.org>
 <3737494.1728921663@sss.pgh.pa.us>
Subject: Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs
 parameters produce incorrect results
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3411410_2037470168.1729073440569"
Archived-At: 
 <https://www.postgresql.org/message-id/292395358.3411411.1729073440569%40wlpnf0212.sys.meshcore.net>
Precedence: bulk

------=_Part_3411410_2037470168.1729073440569
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Tom,

Thank you for this feedback,
Indeed, it works correctly. The problem comes from the other side of the keyboard...
I went a little fast and did not check the length of my input strings which contained "invisible" characters.
After cleaning up the results obtained are as expected.
Really sorry for this false alarm

Regards

Hmm, works for me:

u8=# create extension fuzzystrmatch;
CREATE EXTENSION
u8=# SELECT levenshtein('horses','shorse',1,1,1);
levenshtein
-------------
2
(1 row)

u8=# SELECT levenshtein('horses','shorse',100,10,1);
levenshtein
-------------
6
(1 row)

I confess bafflement about why you're getting wrong answers.
You seem to be using a slightly out of date Postgres, but
none of this code has changed meaningfully since about 2016.
Maybe you hit a compiler bug? Where did you get this copy
of Postgres from --- or if you built it yourself, what build
options did you use?

regards, tom lane


------=_Part_3411410_2037470168.1729073440569
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Tom,<br>
<br>
Thank you for this feedback,<br>
Indeed, it works correctly. The problem comes from the other side of the keyboard...<br>
I went a little fast and did not check the length of my input strings which contained "invisible" characters.<br>
After cleaning up the results obtained are as expected.<br>
Really sorry for this false alarm<br>
<br>
Regards
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">
<div class="gl_quoted">Hmm, works for me:<br>
<br>
u8=# create extension fuzzystrmatch;<br>
CREATE EXTENSION<br>
u8=# SELECT levenshtein('horses','shorse',1,1,1);<br>
levenshtein<br>
-------------<br>
2<br>
(1 row)<br>
<br>
u8=# SELECT levenshtein('horses','shorse',100,10,1);<br>
levenshtein<br>
-------------<br>
6<br>
(1 row)<br>
<br>
I confess bafflement about why you're getting wrong answers.<br>
You seem to be using a slightly out of date Postgres, but<br>
none of this code has changed meaningfully since about 2016.<br>
Maybe you hit a compiler bug? Where did you get this copy<br>
of Postgres from --- or if you built it yourself, what build<br>
options did you use?<br>
<br>
regards, tom lane</div>
</div>

------=_Part_3411410_2037470168.1729073440569--