From: | Durumdara <durumdara(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot delete role because it depends on "default privileges" |
Date: | 2016-10-21 14:31:54 |
Message-ID: | CAEcMXhmG4evh_uwMQuByghzEyR+5B-gP5gzW9rxiE9uMdMZ7gA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Wooooooooooooooooooooow... I found it. The postgres database contained more
default privs. But PGAdmin III nothing say about dependents in it's reports.
Thanks!
2016-10-21 16:19 GMT+02:00 Durumdara <durumdara(at)gmail(dot)com>:
> Dear Tom!
>
> Is there any tool what can show me the dependents or dependencies?
>
> In PGAdmin I don't see any dependencies or dependents... :-(
>
> Thanks
> dd
>
> 2016-10-21 16:08 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
>> Durumdara <durumdara(at)gmail(dot)com> writes:
>> > The DB_X dropped, so I can't choose it as "actual database".
>> > I tried this in a neutral database:
>> > drop owned by role_x;
>> > But nothing happened, the error is same.
>>
>> The error you are reporting is describing default privileges that
>> exist in the *current* database. You need to do DROP OWNED BY
>> in that database (and maybe other ones, but start there).
>>
>> regards, tom lane
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Edilmar LISTAS | 2016-10-21 15:09:02 | Doubts about replication from many servers |
Previous Message | Durumdara | 2016-10-21 14:19:09 | Re: Cannot delete role because it depends on "default privileges" |