MIME-Version: 1.0
From: Dominique Devienne <ddevienne@gmail.com>
Date: Thu, 20 Feb 2025 16:48:20 +0100
Message-ID: <CAFCRh-_3+E3-pmdH+i5jUE-8Z1jJWxxdP3EcFjTbHVWM+oEweg@mail.gmail.com>
Subject: DROP ROLE as SUPERUSER
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a4df33062e94cef6"
Archived-At: <https://www.postgresql.org/message-id/CAFCRh-_3%2BE3-pmdH%2Bi5jUE-8Z1jJWxxdP3EcFjTbHVWM%2BoEweg%40mail.gmail.com>
Precedence: bulk

--000000000000a4df33062e94cef6
Content-Type: text/plain; charset="UTF-8"

Hi. Today I was surprised that REVOKE ALL ON DATABASE FROM ROLE silently
did nothing, even with CASCADE, when I was running it as SUPERUSER,
preventing DROP'ing the ROLE. I had to manually SET ROLE to the GRANTOR, do
the REVOKE, which DID something this time, and then I could DROP the role.

That's hardly convenient :). And I was helping someone else who couldn't
figure out how to drop that role. Isn't there a better way?

I thought SUPERUSER was more powerful that than. Why isn't it?

Thanks, --DD

--000000000000a4df33062e94cef6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi. Today I was surprised that REVOKE ALL ON DATABASE FROM=
 ROLE silently did nothing, even with CASCADE, when I was running it as SUP=
ERUSER, preventing DROP&#39;ing the ROLE. I had to manually SET ROLE to the=
 GRANTOR, do the REVOKE, which DID something this time, and then I could DR=
OP the role.<div><br></div><div>That&#39;s hardly convenient :). And I was =
helping someone else who couldn&#39;t figure out how to drop that role. Isn=
&#39;t there a better way?</div><div><br></div><div>I thought SUPERUSER was=
 more powerful that than. Why isn&#39;t it?</div><div><br></div><div>Thanks=
, --DD</div></div>

--000000000000a4df33062e94cef6--