Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results - Mailing list pgsql-bugs

From bjdev.gthb@laposte.net
Subject Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results
Date
Msg-id 292395358.3411411.1729073440569@wlpnf0212.sys.meshcore.net
Whole thread Raw
In response to Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Tender Wang
Date:
Subject: Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
Next
From: Amit Langote
Date:
Subject: Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault