Re: DROP ROLE blocked by pg_init_privs
| От | Tom Lane |
|---|---|
| Тема | Re: DROP ROLE blocked by pg_init_privs |
| Дата | |
| Msg-id | 1484313.1764115685@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: DROP ROLE blocked by pg_init_privs (immerrr again <immerrr@gmail.com>) |
| Ответы |
Re: DROP ROLE blocked by pg_init_privs
|
| Список | pgsql-general |
immerrr again <immerrr@gmail.com> writes: > Sorry, nvm, I forgot to drop the privileges in the repro. Can confirm, with > 16.9 it works as expected: > ... > The same script with postgres:17 image fails with the error I have been > describing: The missing step here is DROP OWNED BY test_role; You have to use that to get rid of "initial privileges" because neither REVOKE nor ALTER DEFAULT PRIVILEGES will touch existing initial privileges. Pre-v17 didn't account for this properly and would allow you to drop the role anyway, leaving dangling entries behind in pg_init_privs. While those are harmless in isolation, they cause problems for later dump/restore activity. See discussion here: https://www.postgresql.org/message-id/flat/1745535.1712358659%40sss.pgh.pa.us regards, tom lane
В списке pgsql-general по дате отправления: