Re: RFC: Restructuring pg_aggregate
От | Tom Lane |
---|---|
Тема | Re: RFC: Restructuring pg_aggregate |
Дата | |
Msg-id | 18870.1018560401@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: RFC: Restructuring pg_aggregate (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: RFC: Restructuring pg_aggregate
|
Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.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
В списке pgsql-hackers по дате отправления: