Re: Fwd: pg_trgm word_similarity inconsistencies or bug
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Jan Przemysław Wójcik <jan.przemyslaw.wojcik@gmail.com>
Cc: pgsql-bugs@postgresql.org
Date: 2017-11-07T16:24:27Z
Lists: pgsql-bugs, pgsql-hackers
Hi! On Tue, Nov 7, 2017 at 3:51 PM, Jan Przemysław Wójcik < jan.przemyslaw.wojcik@gmail.com> wrote: > Hi, > > my statement about the function usefulness was probably too categorical, > though I had in mind the current name of the function. > > I'm afraid that creating a function that implements quite different > algorithms depending on a global parameter seems very hacky and would lead > to misunderstandings. I do understand the need of backward compatibility, > but I'd opt for the lesser evil. Perhaps a good idea would be to change the > name to 'substring_similarity()' and introduce the new function > 'word_similarity()' later, for example in the next major version release. > Good point. I've no complaints about that. I'm going to propose corresponding patch to the next commitfest. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
Update trigram example in docs to correct state
- 9975c128a1d1 11.0 cited
-
Add strict_word_similarity to pg_trgm module
- be8a7a686627 11.0 landed
-
Rework word_similarity documentation, make it close to actual algorithm.
- aea7c17e86e9 11.0 cited