| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: doc: fast access to server parameters |
| Date: | 2026-08-05 12:47:18 |
| Message-ID: | CAHGQGwG4v+F6_hTKSd3HJ3UYtO0mo6jYP_OmbLVrqxBM6OjFmw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 28, 2026 at 4:37 AM Euler Taveira <euler(at)eulerto(dot)com> wrote:
>
> Hi,
>
> If you want to check a GUC description, you access the "Server Configuration"
> chapter and then need to figure out what is the exact section. Sometimes you
> need a back-and-forth until find the exact GUC. You can click on the section
> 19.X and then browse to find the GUC. I was wondering if there is a better (and
> fast) way to find a GUC.
Isn't the existing index sufficient for jumping from a known GUC name to
its documentation? If some GUCs are missing from the index or are hard to find,
it seems better to improve the index entries than to add a second generated
list of the same items.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shinya Kato | 2026-08-05 13:22:54 | Re: Report oldest xmin source when autovacuum cannot remove tuples |
| Previous Message | Etsuro Fujita | 2026-08-05 12:18:58 | Re: Asynchronous MergeAppend |