Re: [PATCH] DefaultACLs - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [PATCH] DefaultACLs
Date
Msg-id 4ACB401D.1000003@pjmodos.net
Whole thread Raw
In response to Re: [PATCH] DefaultACLs  (Petr Jelinek <pjmodos@pjmodos.net>)
Responses Re: [PATCH] DefaultACLs  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Petr Jelinek napsal(a): <blockquote cite="mid:4ACA7962.7090804@pjmodos.net" type="cite"> Tom Lane napsal(a):
<blockquotecite="mid:5876.1254782904@sss.pgh.pa.us" type="cite"><pre>Petr Jelinek <a href="mailto:pjmodos@pjmodos.net"
moz-do-not-send="true"><pjmodos@pjmodos.net></a>writes: </pre><blockquote type="cite"><pre>Tom Lane napsal(a):
</pre><blockquotetype="cite"><pre>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.     </pre></blockquote></blockquote><blockquote type="cite"><pre>Yeah I am not happy
aboutthis 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.   </pre></blockquote><pre>IIRC it just threw a warning, which didn't seem tremendously
usefulto
 
me. </pre></blockquote><br /> Oh did it ? Then I must have discarded that idea for some reason. I probably didn't want
tobe too pushy there.<br /><br /></blockquote><br /> Now I remember why - consistency with ACLs on object. REASSIGN
OWNEDdoes not drop any GRANTed ACLs on any object, so it seemed appropriate to only drop default ACLs in DROP OWNED BY
alongwith ACLs on objects.<br /><br /><pre class="moz-signature" cols="72">-- 
 
Regards
Petr Jelinek (PJMODOS)</pre>

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [PATCH] DefaultACLs
Next
From: Alvaro Herrera
Date:
Subject: Re: Streaming Replication patch for CommitFest 2009-09