Re: Version 14/15 documentation Section "Alter Default Privileges"

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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-06 08:44:14
Message-ID: ceac8e2df89a5eb1335ad8ce39c6ba0beaeddde3.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

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 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.

I see what you mean. The alternative is to be precise, at the risk of
repeating ourselves:

if omitted, default privileges will be changed for objects created by
the current role.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2023-11-06 15:26:16 Re: Version 14/15 documentation Section "Alter Default Privileges"
Previous Message Michael Banck 2023-11-06 08:32:27 Re: Version 14/15 documentation Section "Alter Default Privileges"

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2023-11-06 09:18:18 Re: Reuse child_relids in try_partitionwise_join was Re: Assert failure on bms_equal(child_joinrel->relids, child_joinrelids)
Previous Message Peter Eisentraut 2023-11-06 08:38:36 Re: pg_resetwal tests, logging, and docs update