Re: Orphaned users in PG16 and above can only be managed by Superusers - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: Orphaned users in PG16 and above can only be managed by Superusers
Date
Msg-id CAE9k0PmFK40LU-nKwGkvEWv5ANsZsH5CAVfQniBO_uzantP1vg@mail.gmail.com
Whole thread Raw
In response to Re: Orphaned users in PG16 and above can only be managed by Superusers  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Thanks, Nathan, for reviewing the patch. Below are my comments inline:

On Thu, Mar 6, 2025 at 1:43 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
>
> * The patch alleges to only block DROP ROLE commands when there exists
>   _both_ admins of the target role and roles for which the target role is
>   an admin.  However, it's not clear to me why both need to be true.  I
>   might be able to glean the reason if I read this thread carefully or
>   spend more time thinking about it, but IMHO that patch itself should make
>   it obvious.  I'd suggest expanding the comment atop
>   check_drop_role_dependency().
>

I'll update the comments above the check_drop_role_dependency()
function to clarify things.

> * Does this introduce any race conditions?  For example, is it possible for
>   the new check to pass and then for a dependency to be added before the
>   drop completes?
>

I believe it is; I may need to adjust the location from where I'm
calling check_drop_role_dependency() to take care of this. I'll
address this in the next patch version. Thanks for bringing up this
concern.

--
With Regards,
Ashutosh Sharma.



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Refactoring postmaster's code to cleanup after child exit
Next
From: Ashutosh Sharma
Date:
Subject: Re: Orphaned users in PG16 and above can only be managed by Superusers