Peter Eisentraut <pete...@gmx.net> writes:
> This ought to show EXECUTE privilege on the new function, but it
> doesn't, because proacl is null, and nothing in the information schema
> handles that specially.
> I've pondered some ways to fix that. One would be to add a variant of
> aclexplode() that takes a parameter telling which catalog the acl datum
> came from, and aclexplode() could then substitute the data received
> acldefault() for null values. The other way would be to handle this
> entirely in the information schema SQL (either using some coalesce calls
> or perhaps a UNION). But that would mean duplicating the knowledge of
> acldefault() in a second remote place. So I'm thinking that handling it
> in aclexplode() would be better.
+1. It would be a really bad idea for the acldefault() logic to be
duplicated someplace else, especially in SQL code where grepping for the
relevant macros wouldn't even find it.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
