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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Francisco Olarte <folarte(at)peoplecall(dot)com>
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 15:06:57
Message-ID: 1551470.1613142417@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Francisco Olarte <folarte(at)peoplecall(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-02-12 15:23:12 Re: BUG #16862: Unexpected result of checking for null "IS NOT NULL" in function
Previous Message Kämpf 2021-02-12 14:52:50 AW: BUG #16859: PostGIS 30 and 31 installation on SLES15 SP2 missing package SFCGAL or gmp