| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "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-21 14:35:19 |
| Message-ID: | CAFCRh--+406OqvQv60Yt9DXzS2cy9EN9Gz4hUx7sVKT9Ui7afQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 21, 2025 at 3:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> > The point I'm trying to make, is that "hunting down" grantor(s) to
> connect
> > to DB(s) to be able to "force drop" a ROLE is a PITA. And I really wish
> > there
> > was an easier way to drop a role in that situation. --DD
>
> REASSIGN OWNED then DROP OWNED is the recommended path.
>
Hi. Am I missing something? foobar does not OWN anything in this case.
So I don't see how these recommendations are relevant to this particular
case. --DD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-02-21 14:44:22 | Re: DROP ROLE as SUPERUSER |
| Previous Message | Tom Lane | 2025-02-21 14:33:56 | Re: DROP ROLE as SUPERUSER |