| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | s(dot)bailey(at)chorusintel(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: CREATE ROLE |
| Date: | 2024-03-27 21:58:48 |
| Message-ID: | ZgSWmPDJ_dWFUObx@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Mar 27, 2024 at 12:52:55AM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-createrole.html
> Description:
>
> https://www.postgresql.org/docs/16/sql-createrole.html
>
> ROLE role_name
> The ROLE clause causes one or more specified existing roles to be
> automatically added as members, with the SET option enabled. This in effect
> makes the new role a “group”. Roles named in this clause with role-level the
> INHERIT attribute will have the INHERIT option enabled in the new
> membership. New memberships will have the ADMIN option disabled.
>
> The following sentence is badly worded:
> Roles named in this clause with role-level the INHERIT attribute will have
> the INHERIT option enabled in the new membership
Yep, fixed in the attached patch, applied back to PG 16 where this typo
was created. Thanks for the report.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| Attachment | Content-Type | Size |
|---|---|---|
| master.diff | text/x-diff | 804 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2024-03-29 23:26:02 | ts_headline performance note |
| Previous Message | PG Doc comments form | 2024-03-27 00:52:55 | CREATE ROLE |