Re: Orphaned users in PG16 and above can only be managed by Superusers

lt was necessary before we proceed with actually dropping the role, starting with the deletion of drop role entries from the system catalogs. I’m aware there’s some code duplication, but I think it should be fine. -- With Regards, Ashutosh Sharma.

Re: Orphaned users in PG16 and above can only be managed by Superusers

Hi, On Thu, Mar 13, 2025 at 11:14 AM Ashutosh Sharma wrote: > > Hi, > > On Wed, Mar 12, 2025 at 9:06 PM Nathan Bossart > wrote: > > > > There are also other ways besides DROP ROLE that roles can end up without > > any admins: > > > >

Re: Orphaned users in PG16 and above can only be managed by Superusers

Hi Nathan, Thanks for the review comment. On Mon, Mar 10, 2025 at 8:31 PM Nathan Bossart wrote: > > On Mon, Mar 10, 2025 at 11:15:04AM +0530, Ashutosh Sharma wrote: > > On Fri, Mar 7, 2025 at 10:55 PM Nathan Bossart > > wrote: > >> I noticed that much of this c

Re: Orphaned users in PG16 and above can only be managed by Superusers

Hi Nathan, On Mon, Mar 10, 2025 at 8:31 PM Nathan Bossart wrote: > > On Mon, Mar 10, 2025 at 11:15:04AM +0530, Ashutosh Sharma wrote: > > On Fri, Mar 7, 2025 at 10:55 PM Nathan Bossart > > wrote: > >> I noticed that much of this code is lifted f

Re: Orphaned users in PG16 and above can only be managed by Superusers

ivilege on role 'c', it's expected that role 'a' will also lose the privilege, as it was inherited from role 'b'. After the ADMIN privilege is revoked, role 'a' will no longer have a dependency on role 'b', so dropping role 'b' should succeed. -- With Regards, Ashutosh Sharma.

Re: Orphaned users in PG16 and above can only be managed by Superusers

the CASCADE/RESTRICT syntax specifically for handling dependent roles, rather than the dependent database objects like tables, views, etc., which can span multiple databases. Please correct me if I’m mistaken or if there’s anything I’ve missed in my understanding. thanks. -- With Regards, Ashutosh

<    1   2   3   4