On Mon, Nov 13, 2023 at 08:33:33PM +0100, Laurenz Albe wrote:
> On Mon, 2023-11-13 at 14:28 -0500, Bruce Momjian wrote:
> > Patch applied back to PG 16.
>
> Great thanks!
>
> I am hopeful that that will reduce people's confusion about this feature.
Agreed!
--
Bruce Momjian https://m
On Mon, 2023-11-13 at 14:28 -0500, Bruce Momjian wrote:
> Patch applied back to PG 16.
Great thanks!
I am hopeful that that will reduce people's confusion about this feature.
Yours,
Laurenz Albe
On Wed, Nov 8, 2023 at 01:12:24PM +0100, Laurenz Albe wrote:
> > I find the above sentence odd. What is its purpose?
>
> I cannot count how many times I have seen the complaint "I have run ALTER
> DEFAULT
> PRIVILEGES, and now when some other user creates a table, the permissions are
> unchange
On Wed, Nov 8, 2023 at 01:12:24PM +0100, Laurenz Albe wrote:
> On Tue, 2023-11-07 at 17:30 -0500, Bruce Momjian wrote:
> > You didn't seem to like my SET ROLE suggestion so I removed it.
>
> I thought that the information that you can use SET ROLE to assume
> the identity of another role is corre
On Tue, 2023-11-07 at 17:30 -0500, Bruce Momjian wrote:
> You didn't seem to like my SET ROLE suggestion so I removed it.
I thought that the information that you can use SET ROLE to assume
the identity of another role is correct, but leads a bit too far
in the manual page of ALTER DEFAULT PRIVILEG
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:
> > +
> > + There is no way to change the default privileges for objects created by
> > + arbitrary roles. You have run ALTER DEFAULT
> > PRIVILEGES
>
> I fin
On Mon, Nov 6, 2023 at 09:53:50PM +0100, Laurenz Albe wrote:
> On Mon, 2023-11-06 at 10:55 -0500, Bruce Momjian wrote:
> > Okay, I think I have good wording for this. I didn't like the wording
> > of other roles, so I restructured that in the attached patch too.
>
> >
> > !Default privi
On Mon, 2023-11-06 at 10:55 -0500, Bruce Momjian wrote:
> Okay, I think I have good wording for this. I didn't like the wording
> of other roles, so I restructured that in the attached patch too.
>
> !Default privileges apply only to the active role; the default
> !privileges of mem
On Mon, Nov 6, 2023 at 09:44:14AM +0100, Laurenz Albe wrote:
> On Sat, 2023-11-04 at 21:14 -0400, Bruce Momjian wrote:
> > > 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
On Mon, Nov 6, 2023 at 09:32:27AM +0100, Michael Banck wrote:
> Hi,
>
> On Sat, Nov 04, 2023 at 09:14:01PM -0400, Bruce Momjian wrote:
> > + There is no way to change the default privileges for objects created by
> > + any role. You have run ALTER DEFAULT PRIVILEGES for
> > all
> > + role
On Sat, 2023-11-04 at 21:14 -0400, Bruce Momjian wrote:
> > 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 futur
Hi,
On Sat, Nov 04, 2023 at 09:14:01PM -0400, Bruce Momjian wrote:
> + There is no way to change the default privileges for objects created by
> + any role. You have run ALTER DEFAULT PRIVILEGES for
> all
> + roles that can create objects whose default privileges should be modified.
That
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
> + target_role; if omitted, th
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
+ target_role; if omitted, the current
+ role is modified.
It is not the role that is modified. Pe
On Sat, Nov 4, 2023 at 07:05:28AM +0100, Laurenz Albe wrote:
> On Fri, 2023-11-03 at 12:53 -0400, Bruce Momjian wrote:
> > I have developed the attached patch on top of the alter default patch I
> > just applied. It is more radical, making FOR ROLE clearer, and also
> > moving my new FOR ROLE tex
On Fri, 2023-11-03 at 12:53 -0400, Bruce Momjian wrote:
> I have developed the attached patch on top of the alter default patch I
> just applied. It is more radical, making FOR ROLE clearer, and also
> moving my new FOR ROLE text up to the first paragraph, and reordering
> the paragraphs to be cle
On Sat, Oct 28, 2023 at 11:01:59AM +0200, Michael Banck wrote:
> On Fri, Oct 27, 2023 at 05:49:42PM +0200, Laurenz Albe wrote:
> > 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
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, Laur
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 +, David Burns wrot
Hi,
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 +, David Burns wrote:
> > >
> > > > Some additional clarity in the versions 1
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 +, David Burns wrote:
> >
> > > Some additional clarity in the versions 14/15 documentation would be
> > > helpful specifically
> > > surrounding the
21 matches
Mail list logo
