From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RFC: Restructuring pg_aggregate |
Date: | 2002-04-11 21:26:41 |
Message-ID: | 18870.1018560401@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Why shouldn't aggregate functions have entries in pg_proc? Then one
>> search would cover both possibilities, and we could eliminate some
>> duplicate code in the parser.
> Furthermore, we could make the new function privileges apply to aggregates
> as well.
GRANT/REVOKE FUNCTION will now work on aggregate functions too (is there
any value in making a variant syntax for aggregates?). However, I
didn't implement enforcement of the EXECUTE privilege yet. I was
slightly bemused to notice that your implementation of it for regular
functions tests the privilege at plan startup but doesn't actually throw
the error until the function is called. What's the point of that?
Seems like we might as well throw the error in init_fcache and not
bother with storing a boolean.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-11 21:39:26 | Re: numeric/decimal docs bug? |
Previous Message | Barry Lind | 2002-04-11 20:56:12 | Re: 7.3 schedule |