Re: Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: David Steele <david@pgmasters.net>
Cc: Teodor Sigaev <teodor@sigaev.ru>, Robert Haas <robertmhaas@gmail.com>, Jan Przemysław Wójcik <jan.przemyslaw.wojcik@gmail.com>, Postgres-Bugs <pgsql-bugs@postgresql.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-03-01T21:26:32Z
Lists: pgsql-bugs, pgsql-hackers
On Thu, Mar 1, 2018 at 11:05 PM, David Steele <david@pgmasters.net> wrote: > On 1/4/18 4:25 PM, Alexander Korotkov wrote: > > > > I just found that patch apply is failed according to > > commitfest.cputube.org <http://commitfest.cputube.org>. I think it's > > because I sent only second patch from patchset in last message. > > Anyway I resend both patches rebased to current master. > > I agree with Teodor (upthread, not quoted here) that the documentation > could use some editing. > > I started to do it myself, but quickly realized I have no knowledge of > the content. I'm afraid I would destroy the meaning while updating the > grammar. > That's to problem. If you're willing to help you can edit the documentation and let me review that it's correct. Also feel free to ask any questions and more explanation from me. Ultimately, we need to have a documentation that any average user can understand, not to mention you :) Anyone understand the subject matter well enough to review the > documentation? > I expect it would be hard to find anybody matching this criteria. But it would be nice to find one though. ------ 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