| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: CREATE ROLE inheritance details |
| Date: | 2024-03-31 06:16:42 |
| Message-ID: | 20240331061642.07@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Jan 30, 2024 at 01:49:42PM -0700, David G. Johnston wrote:
> + The membership grants created by the
> + <literal>IN ROLE</literal>, <literal>ROLE</literal>, and <literal>ADMIN</literal>
> + clauses have the role executing this command as the grantee.
This should be s/grantee/grantor/, right?
> + If unspecified when create a new role membership this defaults to
> + the inheritance attribute of the role being added.
Need s/create/creating/. Missing comma. While phrase "role being added"
isn't wrong, the rest of the paragraph uses "member" and uses "granted role"
to refer to the member-of role. Putting those together:
If unspecified when creating a new role membership, this defaults to the
inheritance attribute of the new member.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2024-04-02 14:40:24 | ALTER TABLE atomicity with sub-commands |
| Previous Message | PG Doc comments form | 2024-03-29 23:26:02 | ts_headline performance note |