Re: pgsql: Fix operator naming in pg_trgm GUC option descriptions

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Fix operator naming in pg_trgm GUC option descriptions
Date: 2019-06-10 17:33:01
Message-ID: CAPpHfdt+vs84Uyfrxuu3i+0XNJO5KgPoHZdMbr7ZLzBiWMAM1g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Jun 10, 2019 at 8:19 PM Alexander Korotkov
<akorotkov(at)postgresql(dot)org> wrote:
> Backpatch-through: 9.4

Sorry, this appears to be wrong. Backpatch was needed only to 9.6.
In 9.5 and earlier there wasn't GUC option. Threshold was operated
just by set_limit()/show_limit() functions.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2019-06-10 19:40:03 Re: pgsql: Stop using spelling "nonexistant".
Previous Message Alexander Korotkov 2019-06-10 17:31:18 pgsql: Fix operator naming in pg_trgm GUC option descriptions