Re: allowing for control over SET ROLE
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Stephen Frost <sfrost@snowman.net>,
Nathan Bossart <nathandbossart@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-11-17T21:52:29Z
Lists: pgsql-hackers
On Tue, Nov 15, 2022 at 7:23 PM Jeff Davis <pgsql@j-davis.com> wrote: > On Tue, 2022-11-15 at 12:07 -0500, Robert Haas wrote: > > If anyone else wants to comment, or if either of those people want to > > comment further, please speak up soon. > > Did you have some thoughts on: > > https://postgr.es/m/a41d606daaaa03b629c2ef0ed274ae3b04a2c266.camel@j-davis.com I mean, I think what we were discussing there could be done, but it's not the approach I like best. That's partly because that was just a back-of-the-envelope sketch of an idea, not a real proposal for something with a clear implementation path. But I think the bigger reason is that, in my opinion, this proposal is more generally useful, because it takes no position on why you wish to disallow SET ROLE. You can just disallow it in some cases and allow it in others, and that's fine. That proposal targets a specific use case, which may make it a better solution to that particular problem, but it makes it unworkable as a solution to any other problem, I believe. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
More documentation update for GRANT ... WITH SET OPTION.
- 3cdf7502f85c 16.0 landed
-
Restrict the privileges of CREATEROLE users.
- cf5eb37c5ee0 16.0 cited
-
Add support for GRANT SET in psql tab completion
- 9d0cf574920f 16.0 landed
-
Add a SET option to the GRANT command.
- 3d14e171e9e2 16.0 landed
-
Allow grant-level control of role inheritance behavior.
- e3ce2de09d81 16.0 cited