Re: BUG #16860: Documentation: GUC Parameters are not explained

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: boshomi(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16860: Documentation: GUC Parameters are not explained
Date: 2021-02-12 08:22:48
Message-ID: CA+bJJbxLWT50CaHmsRjAxJ5DVcqd8FyM7uq1ot3qPENCC7-vXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom:

On Thu, Feb 11, 2021 at 6:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > I am missing a explanation for the abbreviation "GUC" in:
> > in
> > https://www.postgresql.org/docs/current/sepgsql.html#SEPGSQL-PARAMETERS
> > and https://www.postgresql.org/docs/current/pgtrgm.html#id-1.11.7.40.7
> It's defined in appendix L (Acronyms). It would not be sensible to
> duplicate the definition at every usage.

I ( not the OP ) knew the meaning ( although I had forgotten the exact
words ), and managed to find it, but had to do a full search. IMO an
entry in the index could be useful for it, even if it is just an
acronym ( I went to the HTML manual, searched in the TOC, searched in
the first couple server configuration pages, searched in the index and
then resorted to full search and got the acronyms hit in the middle,
it seems a bit hidden for me ).

Francisco Olarte.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pawel Kudzia 2021-02-12 12:35:39 Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Previous Message PG Bug reporting form 2021-02-12 02:45:36 BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function