From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Joel Jacobson <joel(at)compiler(dot)org> |
Cc: | 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-24 21:15:33 |
Message-ID: | CAKFQuwaqM5-Pp3FVD4MeVAEU5_3dyrp5CCnMqVwPOhjo9JPe1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 24, 2024 at 1:49 PM Joel Jacobson <joel(at)compiler(dot)org> wrote:
> How about?
>
> + <para>
> + The linked page uses "permissions" while we consistently use the
> synonym
> + "privileges", to describe the contents of the list. For avoidance of
> + doubt and clarity, these two terms are equivalent in the
> + <productname>PostgreSQL</productname> documentation.
> + </para>
>
> /Joel
I really dislike "For avoidance of doubt and clarity" - and in terms of
being equivalent the following seems like a more accurate description of
reality.
The PostgreSQL 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 "permissions" we are referring to
something that is not covered by the ACL. In routine communication the two
words are often used interchangeably.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2024-06-24 21:17:14 | Re: RFC: Additional Directory for Extensions |
Previous Message | Melanie Plageman | 2024-06-24 20:58:09 | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |