| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add ACL (Access Control List) acronym |
| Date: | 2024-06-26 01:16:55 |
| Message-ID: | CAKFQuwb99OqbPZeMoGC1Q3p-nyChTNd1LHqXidSDyX=R8qz8Gw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 24, 2024 at 10:11 PM Michael Paquier <michael(at)paquier(dot)xyz>
wrote:
> On Tue, Jun 25, 2024 at 12:20:20AM +0200, Joel Jacobson wrote:
> > Thanks, much better. New version attached.
>
> + The <productname>PostgreSQL</productname> documentation, and code,
> refers
> + to the specifications within the ACL as "privileges". This has the
> same
> + meaning as "permissions" on the linked page. Generally if we say
>
> Hmm? A privilege is a property that is part of an ACL, which is
> itself a set made of object types, roles and privileges.
>
So, an ACL is a collection of composite typed things (grantor, grantee,
privileges) and the type name for that composite type is "permission".
That does clear things up, even if we tend to use privilege in cases where
permission is meant.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-06-26 01:30:42 | Re: Should we document how column DEFAULT expressions work? |
| Previous Message | David G. Johnston | 2024-06-26 00:59:01 | Re: [PATCH] Add ACL (Access Control List) acronym |