From: | Yurii Rashkovskii <yrashk(at)gmail(dot)com> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: ALTER ROLE documentation improvement |
Date: | 2023-09-15 21:25:38 |
Message-ID: | CA+RLCQxRyS_=Bf1jUWE0cd-g92-pw7b6cZX+6BXGs0EjJbptTw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Sep 15, 2023 at 1:53 PM Nathan Bossart <nathandbossart(at)gmail(dot)com>
wrote:
> On Fri, Sep 15, 2023 at 11:46:35AM -0700, Yurii Rashkovskii wrote:
> > It appears that 16.0 improved some of the checks in ALTER ROLE.
> Previously,
> > it was possible to do the following (assuming current_user is a bootstrap
> > user):
> >
> > ```
> > ALTER ROLE current_user NOSUPERUSER
> > ```
> >
> > As of 16.0, this produces an error:
> >
> > ```
> > ERROR: permission denied to alter role
> > DETAIL: The bootstrap user must have the SUPERUSER attribute.
> > ```
> >
> > The attached patch documents this behavior by providing a bit more
> > clarification to the following statement:
> >
> > "Database superusers can change any of these settings for any role."
>
> I think this could also be worth a mention in the glossary [0]. BTW the
> glossary calls this role the "bootstrap superuser", but the DETAIL message
> calls it the "bootstrap user". Perhaps we should standardize on one name.
>
> [0] https://www.postgresql.org/docs/devel/glossary.html
>
>
Thank you for the feedback. I've updated the glossary and updated the
terminology to be consistent. Please see the new patch attached.
--
Y.
Attachment | Content-Type | Size |
---|---|---|
0001-Improve-ALTER-ROLE-documentation-to-document-current-v2.patch | application/octet-stream | 5.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Yurii Rashkovskii | 2023-09-15 21:36:16 | Re: SET ROLE documentation improvement |
Previous Message | Tom Lane | 2023-09-15 21:14:45 | Re: JSON Path and GIN Questions |