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

From Petr Jelinek
Subject Re: [PATCH] DefaultACLs
Date
Msg-id 4ACA76AE.3090402@pjmodos.net
Whole thread Raw
In response to Re: [PATCH] DefaultACLs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] DefaultACLs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane napsal(a): <blockquote cite="mid:18007.1254771245@sss.pgh.pa.us" type="cite"><pre wrap="">Petr Jelinek <a
class="moz-txt-link-rfc2396E"href="mailto:pjmodos@pjmodos.net"><pjmodos@pjmodos.net></a> writes:
</pre><blockquotetype="cite"><pre wrap="">[ latest default-ACLs patch ]   </pre></blockquote><pre wrap="">
 
Applied with a fair amount of editorial polishing.  Notably I changed
the permissions requirements a bit: </pre></blockquote><br /> Thank you very much Tom.<br /><br /><blockquote
cite="mid:18007.1254771245@sss.pgh.pa.us"type="cite"><pre wrap="">One thing that seems like it's likely to be an
annoyancein practice
 
is the need to explicitly do DROP OWNED BY to get rid of pg_default_acl
entries for a role to be dropped.  But I can't see any very good way
around that, since the entries might be in some other database.  One
thing that might at least reduce the number of keystrokes is to have
REASSIGN OWNED act as DROP OWNED BY for default ACLs.  I can't convince
myself whether that's a good idea though, so I left it as-is for the
moment. </pre></blockquote><br /> Yeah I am not happy about this either but there is not much we can do about it. Btw I
thinkin the version I sent in REASSIGN OWNED acted as DROP OWNED for default ACLs.<br /><br /><pre
class="moz-signature"cols="72">-- 
 
Regards
Petr Jelinek (PJMODOS)</pre>

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot Standby on git
Next
From: Heikki Linnakangas
Date:
Subject: Re: 8.5 TODO: any info on "Create dump tool for write-ahead logs..." in PITR section (1.4)?