Horton

Re: allowing for control over SET ROLE

Erik Rijkers <er@xs4all.nl>

View thread View on postgr.es
From: Erik Rijkers <er@xs4all.nl>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Stephen Frost <sfrost@snowman.net>, Nathan Bossart <nathandbossart@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-11-19T05:28:11Z
Lists: pgsql-hackers 
Op 18-11-2022 om 22:19 schreef Robert Haas:
> On Fri, Nov 18, 2022 at 1:50 PM Erik Rijkers <er@xs4all.nl> wrote:
>> In grant.sgml,
>>
>>     'actualy permisions'
>>
>> looks a bit unorthodox.
> 
> Fixed that, and the other mistake Álvaro spotted, and also bumped
> catversion because I forgot that earlier.

Sorry to be nagging but

   'permisions'  should be
   'permissions'

as well.


And as I'm nagging anyway: I also wondered whether the word order could 
improve:

- Word order as it stands:
However, the actual permissions conferred depend on the options 
associated with the grant.

-- maybe better:
However, the permissions actually conferred depend on the options 
associated with the grant.

But I'm not sure.


Thanks,

Erik

Thanks,

Erik

Commits

  1. More documentation update for GRANT ... WITH SET OPTION.

  2. Restrict the privileges of CREATEROLE users.

  3. Add support for GRANT SET in psql tab completion

  4. Add a SET option to the GRANT command.

  5. Allow grant-level control of role inheritance behavior.