We have got a whole bunch of functions in the system that accept
arguments of type internal, where the actual meaning of internal
varies wildly (it's generally some non-SQL-visible data structure).
While (I believe that) SQL users cannot call any such functions
directly, they could still cause all
On Aug 15, 2008, at 15:12, Tom Lane wrote:
The cleanest solution I can think of is to invent some more
pseudotypes
that act just like INTERNAL, and then to require non-privileged CREATE
commands to reference functions that take one of these types instead
of bare INTERNAL. There is a