Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold" - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold"
Date
Msg-id CAPpHfdsLxzNT3jC6gPa3R5tN2V2n3zmGhqHGSWhUNsppRJRQmQ@mail.gmail.com
Whole thread Raw
In response to Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold"  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: doc: pg_trgm missing description for GUC"pg_trgm.strict_word_similarity_threshold"
Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold"
List pgsql-hackers
On Sat, Jun 8, 2019 at 8:17 PM Alexander Korotkov
<a.korotkov@postgrespro.ru> wrote:
> 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.

Pushed!

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



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: proposal: new polymorphic types - commontype and commontypearray
Next
From: Dmitry Dolgov
Date:
Subject: Re: fix psql \conninfo & \connect when using hostaddr