Feedback-ID: i76984098:Fastmail
Message-ID: <c09df100-6d68-4a86-901f-e1c11a27da27@aklaver.com>
Date: Mon, 24 Jun 2024 17:03:32 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: schema privileges and drop role
To: Matt Zagrabelny <mzagrabe@d.umn.edu>,
 "pgsql-general@postgresql.org >> PG-General Mailing List"
 <pgsql-general@postgresql.org>
References: <CAOLfK3Wx2VMhNONFpNpnA0LCMXpQgmSadGicJ3K+LF+ayeTWxQ@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAOLfK3Wx2VMhNONFpNpnA0LCMXpQgmSadGicJ3K+LF+ayeTWxQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/c09df100-6d68-4a86-901f-e1c11a27da27%40aklaver.com>
Precedence: bulk

On 6/24/24 17:00, Matt Zagrabelny wrote:
> Greetings,
> 
> I have a database that I recently changed the ownership for and now I am 
> attempting to drop the previous owner of the database:
> 
> test_db=# drop ROLE legacy_owner;
> ERROR:  role "legacy_owner" cannot be dropped because some objects 
> depend on it
> DETAIL:  privileges for schema public
> 
> I don't know where to look to find out what I need to alter to be able 
> to remove the legacy role and internet searches came up fruitless.

Generally best to start with the docs:

https://www.postgresql.org/docs/current/sql-droprole.html

"A role cannot be removed if it is still referenced in any database of 
the cluster; an error will be raised if so. Before dropping the role, 
you must drop all the objects it owns (or reassign their ownership) and 
revoke any privileges the role has been granted on other objects. The 
REASSIGN OWNED and DROP OWNED commands can be useful for this purpose; 
see Section 22.4 for more discussion."

> 
> Does anyone have any hints or advice on where to look?
> 
> Thanks for the help!
> 
> -m

-- 
Adrian Klaver
adrian.klaver@aklaver.com