Re: schema privileges and drop role
От | Adrian Klaver |
---|---|
Тема | Re: schema privileges and drop role |
Дата | |
Msg-id | c09df100-6d68-4a86-901f-e1c11a27da27@aklaver.com обсуждение исходный текст |
Ответ на | schema privileges and drop role (Matt Zagrabelny <mzagrabe@d.umn.edu>) |
Ответы |
Re: schema privileges and drop role
|
Список | pgsql-general |
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
В списке pgsql-general по дате отправления: