elein wrote:
>An untrusted language is so because of what it can do and cannot do.
>An untrusted language cannot access the filesystem, for example.
>
>WHO writes and runs untrusted and trusted procedures is a different
>thing. It is the security mechanism meant to restrict writting
>and running the functions written in a trusted/untrusted language.
>
>
Ok, that makes a lot of sense. I read the documentation: "3.4.1
Installing Procedural Languages". It is a bit vague on what an untrusted
language should be prevented from doing. "do not allow access to
database server internals or the file system" is what it says. How about
network access? Is there a more canonical definition somewhere that I
can read ?
Regards,
Thomas Hallgren