From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: improve predefined roles documentation |
Date: | 2024-06-13 20:05:33 |
Message-ID: | CAKFQuwZiyeR08_jsHAvaWSCQ+tyf4sCwrBn_EX5xFYwhKX6Ycw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 13, 2024 at 12:48 PM Nathan Bossart <nathandbossart(at)gmail(dot)com>
wrote:
> I think we could improve matters by abandoning the table and instead
> documenting these roles more like we document GUCs, i.e., each one has a
> section below it where we can document it in as much detail as we want.
>
>
One of the main attributes for the GUCs is their category. If we want to
improve organization we'd need to assign categories first. We already
implicitly do so in the description section where we do group them together
and explain why - but it is all informal. But getting rid of those
groupings and descriptions and isolating each role so it can be linked to
more easily seems like a net loss in usability.
I'm against getting rid of the table. If we do add authoritative
subsection anchors we should just do like we do in System Catalogs and make
the existing table name values hyperlinks to those newly added anchors.
Breaking the one table up into multiple tables along category lines is
something to consider.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-06-13 20:06:13 | Re: RFC: adding pytest as a supported test framework |
Previous Message | Robert Haas | 2024-06-13 20:04:04 | Re: RFC: adding pytest as a supported test framework |