Horton

Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold"

Alexander Korotkov <a.korotkov@postgrespro.ru>

View thread View on postgr.es
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Ian Barwick <ian.barwick@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>, Masahiko Sawada <sawada.mshk@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-06-08T17:17:40Z
Lists: pgsql-hackers 
On Fri, Jun 7, 2019 at 6:02 PM Ian Barwick <ian.barwick@2ndquadrant.com> wrote:
> On 6/7/19 9:00 PM, Michael Paquier wrote:
> > On Fri, Jun 07, 2019 at 03:44:14PM +0900, Masahiko Sawada wrote:
>  > Or is that not worth bothering except on HEAD?  Thoughts?
>
> Personally I don't think it's that critical, but not bothered either way.
> Presumably no-one has complained so far anyway (I only chanced upon the missing
> GUC description because I was poking about looking for examples of custom
> GUC handling...)

I think it worth maintaining consistent documentation and GUC
descriptions in back branches.  So, I'm +1 for backpatching.

I'm going to commit all 3 patches (documentation, GUC description,
documentation indentation) on no objections.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Remove pg_trgm.strict_word_similarity_threshold doc from 9.6 and 10

  2. Add docs of missing GUC to pgtrgm.sgml

  3. Fix docs indentation in pgtrgm.sgml

  4. Fix operator naming in pg_trgm GUC option descriptions

  5. Add strict_word_similarity to pg_trgm module