pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16860: Documentation: GUC Parameters are not explained
4+ messages / 3 participants
[nested] [flat]

* BUG #16860: Documentation: GUC Parameters are not explained
@ 2021-02-10 22:17 PG Bug reporting form <noreply@postgresql.org>
  2021-02-11 17:18 ` Re: BUG #16860: Documentation: GUC Parameters are not explained Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: PG Bug reporting form @ 2021-02-10 22:17 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: boshomi@gmail.com

The following bug has been logged on the website:

Bug reference:      16860
Logged by:          Boshomi
Email address:      boshomi@gmail.com
PostgreSQL version: 13.1
Operating system:   all
Description:        

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

A link to https://www.postgresql.org/docs/current/config-setting.html would
be helpful.



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: BUG #16860: Documentation: GUC Parameters are not explained
  2021-02-10 22:17 BUG #16860: Documentation: GUC Parameters are not explained PG Bug reporting form <noreply@postgresql.org>
@ 2021-02-11 17:18 ` Tom Lane <tgl@sss.pgh.pa.us>
  2021-02-12 08:22   ` Re: BUG #16860: Documentation: GUC Parameters are not explained Francisco Olarte <folarte@peoplecall.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2021-02-11 17:18 UTC (permalink / raw)
  To: boshomi@gmail.com; +Cc: pgsql-bugs@lists.postgresql.org

PG Bug reporting form <noreply@postgresql.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.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: BUG #16860: Documentation: GUC Parameters are not explained
  2021-02-10 22:17 BUG #16860: Documentation: GUC Parameters are not explained PG Bug reporting form <noreply@postgresql.org>
  2021-02-11 17:18 ` Re: BUG #16860: Documentation: GUC Parameters are not explained Tom Lane <tgl@sss.pgh.pa.us>
@ 2021-02-12 08:22   ` Francisco Olarte <folarte@peoplecall.com>
  2021-02-12 15:06     ` Re: BUG #16860: Documentation: GUC Parameters are not explained Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Francisco Olarte @ 2021-02-12 08:22 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: boshomi@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

Tom:

On Thu, Feb 11, 2021 at 6:18 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> PG Bug reporting form <noreply@postgresql.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.





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: BUG #16860: Documentation: GUC Parameters are not explained
  2021-02-10 22:17 BUG #16860: Documentation: GUC Parameters are not explained PG Bug reporting form <noreply@postgresql.org>
  2021-02-11 17:18 ` Re: BUG #16860: Documentation: GUC Parameters are not explained Tom Lane <tgl@sss.pgh.pa.us>
  2021-02-12 08:22   ` Re: BUG #16860: Documentation: GUC Parameters are not explained Francisco Olarte <folarte@peoplecall.com>
@ 2021-02-12 15:06     ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2021-02-12 15:06 UTC (permalink / raw)
  To: Francisco Olarte <folarte@peoplecall.com>; +Cc: boshomi@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

Francisco Olarte <folarte@peoplecall.com> writes:
> 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 ).

Hmm.  I'd supposed that the entries in the acronym list (and the
glossary, now that we've got that ... I wonder why they are separate)
had <indexterm>s, but now I see they don't.  I would not be opposed to
adding index entries.

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2021-02-12 15:06 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-02-10 22:17 BUG #16860: Documentation: GUC Parameters are not explained PG Bug reporting form <noreply@postgresql.org>
2021-02-11 17:18 ` Tom Lane <tgl@sss.pgh.pa.us>
2021-02-12 08:22   ` Francisco Olarte <folarte@peoplecall.com>
2021-02-12 15:06     ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox