On Friday, February 21, 2025, Dominique Devienne <ddevie...@gmail.com> wrote:
> On Fri, Feb 21, 2025 at 3:33 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > >> Dominique Devienne <ddevie...@gmail.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 “drop owned”: Any privileges granted to the given roles on objects in the current database or on shared objects (databases, tablespaces, configuration parameters) will also be revoked. So, the command does more than the name suggests. David J.
