Date: Thu, 13 Jun 2024 15:11:15 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: improve predefined roles documentation
Message-ID: <ZmtSY6w4dw8um9fV@nathan>
References: <ZmtM-4-eRtq8DRf6@nathan>
 <CAKFQuwZiyeR08_jsHAvaWSCQ+tyf4sCwrBn_EX5xFYwhKX6Ycw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKFQuwZiyeR08_jsHAvaWSCQ+tyf4sCwrBn_EX5xFYwhKX6Ycw@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/ZmtSY6w4dw8um9fV%40nathan>
Precedence: bulk

On Thu, Jun 13, 2024 at 01:05:33PM -0700, David G. Johnston wrote:
> 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.

What I had in mind is that we would retain these groupings.  I agree that
isolating roles like pg_read_all_data and pg_write_all_data would be no
good.

-- 
nathan