On Mon, Jan 09, 2012 at 08:23:59PM +0200, Peter Eisentraut wrote:
> On mån, 2012-01-02 at 06:43 +0200, Peter Eisentraut wrote:
>> I figured the best and most flexible way to address this is to export
>> acldefault() as an SQL function and replace
>> aclexplode(proacl)
>> with
>> aclexplo
On mån, 2012-01-02 at 06:43 +0200, Peter Eisentraut wrote:
> I figured the best and most flexible way to address this is to export
> acldefault() as an SQL function and replace
>
> aclexplode(proacl)
>
> with
>
> aclexplode(coalesce(proacl, acldefault('f', proowner)))
>
> where 'f' here
On Jan 1, 2012, at 10:43 PM, Peter Eisentraut wrote:
> I figured the best and most flexible way to address this is to export
> acldefault() as an SQL function and replace
>
>aclexplode(proacl)
>
> with
>
>aclexplode(coalesce(proacl, acldefault('f', proowner)))
It would be nice to provid
On sön, 2011-11-27 at 17:29 -0500, Tom Lane wrote:
> Peter Eisentraut 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
Peter Eisentraut 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 param
