Re: How to drop user if objects depend on it

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Andrus <kobruleht2(at)hot(dot)ee>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to drop user if objects depend on it
Date: 2015-10-07 17:20:42
Message-ID: 5615546A.9060708@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/07/2015 09:50 AM, Andrus wrote:
>>> ALTER DEFAULT PRIVILEGES IN SCHEMA public,firma1 GRANT all ON TABLES TO
>>> vantaa;
>> I am not sure that REASSIGN OWNED will get rid of default-privilege
>> specifiers --- you might have to reverse this step separately.
>> In general, REASSIGN OWNED has to be done by a role that has privileges
>> of (is a member of) both the source and target roles. Superusers are
>> considered members of all roles, so that's how come it works for them.
>
> I tried as superuser:
>
> reassign owned by farukkugay to postgres;
> ALTER DEFAULT PRIVILEGES IN SCHEMA public,firma2 revoke all ON TABLES
> from farukkugay;
> drop user farukkugay ;
>
> but got error
>
> ERROR: role "farukkugay" cannot be dropped because some objects depend
> on it
> SQL state: 2BP01
> Detail: privileges for schema public

Above you revoked DEFAULT PRIVILEGES which applies to objects created in
future. You still probably have PRIVILEGES assigned to farukkugay on the
public schema. So in psql do:

\dn+ public

>
> How to to delete user ?
>
> Andrus.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-10-07 17:25:16 Re: postgres standby won't start
Previous Message Adrian Klaver 2015-10-07 17:15:03 Re: using postgresql for session