postgres.git / summary / log / commit / refs
commit 476ba1ec98a70a67bad8af7d178fb56e3df5aa9b
Author: Alexander Korotkov <akorotkov@postgresql.org>
Date: Wed Jun 13 15:31:18 2018 +0000
First released in: 11.0, 9.6.10, 10.5
Documentation improvement for pg_trgm
Documentation of word_similarity() and strict_word_similarity() functions
contains some vague wordings which could confuse users. This patch makes
those wordings more clear. word_similarity() was introduced in PostgreSQL 9.6,
and corresponding part of documentation needs to be backpatched.
Author: Bruce Momjian, Alexander Korotkov
Discussion: https://postgr.es/m/20180526165648.GB12510%40momjian.us
Backpatch: 9.6, where word_similarity() was introduced
doc/src/sgml/pgtrgm.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/pgtrgm.sgml b/doc/src/sgml/pgtrgm.sgml
index 2613c7a3d5c..350da77104e 100644
--- a/doc/src/sgml/pgtrgm.sgml
+++ b/doc/src/sgml/pgtrgm.sgml
@@ -153,8 +153,8 @@
This function returns a value that can be approximately understood as the
greatest similarity between the first string and any substring of the second
string. However, this function does not add padding to the boundaries of
- the extent. Thus, a whole word match gets a higher score than a match with
- a part of the word.
+ the extent. Thus, the number of additional characters present in the
+ second string is not considered, except for the mismatched word boundry.
</para>
<table id="pgtrgm-op-table">
[parent: 2ce64caaf793]