| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DROP ROLE as SUPERUSER |
| Date: | 2025-02-20 16:29:40 |
| Message-ID: | CAKFQuwYxPq4UNkiRODjQu8KkqOE9G0r1CpoX6ZvfiGab62N9dw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 20, 2025 at 9:21 AM Dominique Devienne <ddevienne(at)gmail(dot)com>
wrote:
> But that's not much better. It's basically like the SET ROLE to the
> GRANTOR I did.
> I guess what I want is GRANTED BY ANYONE! And not have to figure out
> GRANTOR(s).
>
Your stated use case is dropping a role. Does the combination of reassign
and drop owned not fulfill the requirements?
https://www.postgresql.org/docs/current/role-removal.html
Also, you had to know the role you wanted to drop so you already figured
out the grantor.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-02-20 16:52:18 | Re: DROP ROLE as SUPERUSER |
| Previous Message | Dominique Devienne | 2025-02-20 16:21:13 | Re: DROP ROLE as SUPERUSER |