From: | Michael Banck <mbanck(at)gmx(dot)net> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | 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-10-28 09:01:59 |
Message-ID: | 653cce08.050a0220.a10fb.7878@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
Hi,
On Fri, Oct 27, 2023 at 05:49:42PM +0200, Laurenz Albe wrote:
> On Fri, 2023-10-27 at 11:34 +0200, Michael Banck wrote:
> > On Fri, Oct 27, 2023 at 09:03:04AM +0200, Laurenz Albe wrote:
> > > On Fri, 2022-11-04 at 10:49 +0100, Laurenz Albe wrote:
> > > > On Thu, 2022-11-03 at 11:32 +0100, Laurenz Albe wrote:
> > > > > On Wed, 2022-11-02 at 19:29 +0000, David Burns wrote:
> > > > > > Some additional clarity in the versions 14/15 documentation
> > > > > > would be helpful specifically surrounding the "target_role"
> > > > > > clause for the ALTER DEFAULT PRIVILEGES command. To the
> > > > > > uninitiated, the current description seems vague. Maybe
> > > > > > something like the following would help:
> > > >
> > > > After some more thinking, I came up with the attached patch.
> > >
> > I think something like this is highly useful because I have also seen
> > people very confused why default privileges are not applied.
> >
> > However, maybe it could be made even clearer if also the main
> > description is amended, like
> >
> > "You can change default privileges only for objects that will be created
> > by yourself or by roles that you are a member of (via target_role)."
> >
> > or something.
>
> True. I have done that in the attached patch.
> In this patch, it is mentioned *twice* that ALTER DEFAULT PRIVILEGES
> only affects objects created by the current user. I thought that
> would not harm, but if it is too redundant, I can remove the second
> mention.
I think it is fine, and I have marked the patch as ready-for-committer.
I think it should be applied to all branches, not just 14/15 as
mentioned in the subject.
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-10-28 16:18:50 | Re: "22.3. Template Databases" documentation is incomplete |
Previous Message | Laurenz Albe | 2023-10-28 08:53:58 | Re: unnest multirange, returned order |
From | Date | Subject | |
---|---|---|---|
Next Message | Erki Eessaar | 2023-10-28 09:27:33 | Issues with Information_schema.views |
Previous Message | John Naylor | 2023-10-28 08:56:42 | Re: [PoC] Improve dead tuple storage for lazy vacuum |