Re: BUG #17062: Assert failed in RemoveRoleFromObjectPolicy() on DROP OWNED policy applied to duplicate role
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Michael Paquier <michael@paquier.xyz>, exclusion@gmail.com,
pgsql-bugs@lists.postgresql.org
Date: 2021-06-18T18:37:00Z
Lists: pgsql-bugs
Stephen Frost <sfrost@snowman.net> writes: > I haven’t had a chance to delve into this but as far as the question above > goes- short answer is yes, there was generally an idea that we don’t want > policies just disappearing. Also- we don’t allow a role to be dropped when > there are GRANT’d privileges, users have to go REVOKE any privileges that > reference the role. But shouldn't DROP OWNED BY clean those out for you? If you've got the right to get rid of the role, ISTM that that should certainly include the right to get rid of grants to it. regards, tom lane
Commits
-
Remove unnecessary failure cases in RemoveRoleFromObjectPolicy().
- fea89d64e8e4 11.13 landed
- f851696a21b2 12.8 landed
- f5b780c45ca6 10.18 landed
- ba815f00a0ce 13.4 landed
- 9c7a150aec71 9.6.23 landed
- 5a0f1c8c0193 14.0 landed
-
Fix misbehavior of DROP OWNED BY with duplicate polroles entries.
- ea5ae3ae1ab0 11.13 landed
- d21fca084356 14.0 landed
- c58a41605ffa 12.8 landed
- b7e3a440775b 10.18 landed
- 33af10c598e2 13.4 landed
- 0b29b41e5b96 9.6.23 landed