Skip to content

Commit 476ba1e

Browse files
committed
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
1 parent 2ce64ca commit 476ba1e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/pgtrgm.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,8 +153,8 @@
153153
This function returns a value that can be approximately understood as the
154154
greatest similarity between the first string and any substring of the second
155155
string. However, this function does not add padding to the boundaries of
156-
the extent. Thus, a whole word match gets a higher score than a match with
157-
a part of the word.
156+
the extent. Thus, the number of additional characters present in the
157+
second string is not considered, except for the mismatched word boundry.
158158
</para>
159159

160160
<table id="pgtrgm-op-table">

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy