From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: improve predefined roles documentation |
Date: | 2024-06-25 16:28:18 |
Message-ID: | ZnrwIvvjZXSegoVa@nathan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 25, 2024 at 12:16:30PM -0400, Robert Haas wrote:
> pg_database_owner is a predefined role for which membership consists,
> implicitly, of the current database owner. It cannot be granted
> membership in any role, and no role can be granted membership in
> pg_database_owner. However, like any role, it can own objects or
> receive grants of access privileges. Consequently, once
> pg_database_owner has rights within a template database, each owner of
> a database instantiated from that template will exercise those rights.
> Initially, this role owns the public schema, so each database owner
> governs local use of the schema.
The main difference between this and the existing documentation is that the
sentence on membership has been rephrased and moved to earlier in the
paragraph. I think this helps the logical flow a bit. We first talk about
implicit membership, then explicit membership, then we talk about
privileges and the consequences of those privileges, and finally we talk
about the default privileges. So, WFM.
--
nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-06-25 16:31:11 | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |
Previous Message | Robert Haas | 2024-06-25 16:16:30 | Re: improve predefined roles documentation |