| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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-08 06:56:02 |
| Message-ID: | 654b3102.170a0220.c794a.1f5b@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Hi,
On Tue, Nov 07, 2023 at 05:30:20PM -0500, Bruce Momjian wrote:
> On Mon, Nov 6, 2023 at 09:53:50PM +0100, Laurenz Albe wrote:
> > + <para>
> > + There is no way to change the default privileges for objects created by
> > + arbitrary roles. You have run <command>ALTER DEFAULT PRIVILEGES</command>
>
> I find the above sentence odd. What is its purpose?
I guess it is to address the main purpose of this patch/confusion with
users: they believe setting DEFAULT PRIVILEGES will set grants
accordingly for all objects created in the future, no matter who creates
them. So hammering in that this is not the case seems fine from my side
(modulo the "You have to run" typo).
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-11-08 11:58:58 | Re: Another user complaint regarding visibility of pg_catalog data |
| Previous Message | Bruce Momjian | 2023-11-07 22:30:20 | Re: Version 14/15 documentation Section "Alter Default Privileges" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2023-11-08 06:56:09 | Re: Infinite Interval |
| Previous Message | Peter Smith | 2023-11-08 06:55:37 | ensure, not insure |