KaiGai Kohei <kaigai@kaigai.gr.jp> writes:
> Is it an expected behavior that PostgreSQL tries to execute foo() with
> privileges of the owner of language call handler because of its security
> definer property? This server crash is just a result.
A language call handler has no function properties of its own --- which
is why attaching SECURITY DEFINER to it is both useless and meaningless.
The appropriate function properties for any call are those of the user
function being called, which the handler is merely a support for.
You could argue that we should put call handlers into their own table
instead of pg_proc, since they aren't really user-callable functions;
that would prevent people from thinking that something like this is
sane. However, they share just enough infrastructure with real
functions that it didn't seem worth doing it that way.
I see no value whatsoever in making the world safe for people to attach
SECURITY DEFINER to handlers. It's an incorrect declaration, and
superusers need to know better than to declare C functions with
incorrect properties.
regards, tom lane
