On Thu, Nov 10, 2011 at 3:17 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On ons, 2011-11-09 at 00:21 -0500, Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>> > Let me put this differently. Should we either continue to hardcode the
>> > default privileges in the acldefault() function, or should we instead
>> > initialize the system catalogs with an entry in pg_default_acl as though
>> > ALTER DEFAULT PRIVILEGES GRANT USAGE ON TYPES TO PUBLIC; had been
>> > executed?
>>
>> If you're proposing to replace acldefault() with a catalog lookup,
>> I vote no. I think that's a performance hit with little redeeming
>> social value.
>
> No, I'm pondering having pg_default_acl initialized so that newly
> created types have explicit USAGE privileges in their typacl column, so
> acldefault() wouldn't be needed. (And builtin types would have their
> typacl initialized analogously.) I suppose this is how we might have
> done it if we had invented ALTER DEFAULT PRIVILEGES first.
I'm not convinced. That's a lot of catalog clutter for no benefit.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
