| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Michael Banck <mbanck(at)gmx(dot)net>, David Burns <david(dot)burns(at)fedex(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Version 14/15 documentation Section "Alter Default Privileges" |
| Date: | 2023-11-05 01:14:01 |
| Message-ID: | ZUbsWcPypVORlYCg@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Sat, Nov 4, 2023 at 10:12:42PM +0100, Laurenz Albe wrote:
> On Sat, 2023-11-04 at 14:20 -0400, Bruce Momjian wrote:
> > Yes, I see your point. Updated patch attached.
>
> Almost perfect, except:
>
> + Change default privileges for objects created by
> + <replaceable>target_role</replaceable>; if omitted, the current
> + role is modified.
>
> It is not the role that is modified. Perhaps:
>
> [...]; if omitted, the current role is used.
Sure, attached. Here is the issue I have though, we are really not
changing default privileges for objects created in the future, we are
changing the role _now_ so future objects will have different default
privileges, right? I think wording like the above is kind of odd.
--
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 |
|---|---|---|
| role.diff | text/x-diff | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Banck | 2023-11-06 08:32:27 | Re: Version 14/15 documentation Section "Alter Default Privileges" |
| Previous Message | David G. Johnston | 2023-11-04 22:32:25 | Re: jsonb array accessors |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2023-11-05 11:52:09 | Re: MERGE ... RETURNING |
| Previous Message | Michael Paquier | 2023-11-05 00:03:06 | Re: A recent message added to pg_upgade |