From: Tom Lane <tgl@sss.pgh.pa.us>
To: Francisco Olarte <folarte@peoplecall.com>
Cc: boshomi@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16860: Documentation: GUC Parameters are not explained
Date: Fri, 12 Feb 2021 10:06:57 -0500
Message-ID: <1551470.1613142417@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+bJJbxLWT50CaHmsRjAxJ5DVcqd8FyM7uq1ot3qPENCC7-vXw@mail.gmail.com>
References: <16860-3c4cef71e32b4233@postgresql.org>
<1452087.1613063895@sss.pgh.pa.us>
<CA+bJJbxLWT50CaHmsRjAxJ5DVcqd8FyM7uq1ot3qPENCC7-vXw@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, folarte@peoplecall.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16860: Documentation: GUC Parameters are not explained
In-Reply-To: <1551470.1613142417@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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