Re: [PATCH] DefaultACLs

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Petr Jelinek <pjmodos(at)pjmodos(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jan Urban'ski <wulczer(at)wulczer(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] DefaultACLs
Date: 2009-10-06 14:26:39
Message-ID: 20091006142639.GF5929@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Petr Jelinek escribió:
> Petr Jelinek napsal(a):
> >Tom Lane napsal(a):
> >>Petr Jelinek <pjmodos(at)pjmodos(dot)net> <mailto:pjmodos(at)pjmodos(dot)net> writes:
> >>>Tom Lane napsal(a):
> >>>>One thing that seems like it's likely to be an annoyance in practice
> >>>>is the need to explicitly do DROP OWNED BY to get rid of pg_default_acl
> >>>>entries for a role to be dropped.
> >>>Yeah I am not happy about this either but there is not much we
> >>>can do about it. Btw I think in the version I sent in REASSIGN
> >>>OWNED acted as DROP OWNED for default ACLs.
> >>IIRC it just threw a warning, which didn't seem tremendously useful to
> >>me.
> >
> >Oh did it ? Then I must have discarded that idea for some reason.
> >I probably didn't want to be too pushy there.
>
> Now I remember why - consistency with ACLs on object. REASSIGN OWNED
> does not drop any GRANTed ACLs on any object, so it seemed
> appropriate to only drop default ACLs in DROP OWNED BY along with
> ACLs on objects.

That seems reasonable to me too ...

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2009-10-06 14:29:42 Re: moving system catalogs to another tablespace
Previous Message Alvaro Herrera 2009-10-06 14:24:50 Re: Patch: create or replace language