elein <elein(at)varlena(dot)com> writes:
> Perhaps this should be asked on the interfaces list, but...
> Exactly what functions are prohibited (or acceptable)
> for a pl language in PostgreSQL to become trusted?
> Is the exact criteria list documented somewhere?
We don't have a formal definition, but I'd say a minimum requirement
is that a function written in a trusted PL language cannot cause any
outside-the-database actions to be attempted by the backend (such as
trying to read or write any files in the server's filesystem). A
trusted-PL language should be able to define arbitrary self-contained
computations (arithmetic, pattern-matching, or what have you), and it
should be able to access the database at the same level as regular
SQL commands. It should not be able to bypass the SQL abstractions nor
execute any OS-level operations using the postgres user's privileges.
> Since C is wide open, why is it considered trusted,
> or is it?
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Joe Conway||Date: 2003-06-28 03:32:22|
|Subject: Re: Missing array support|
|Previous:||From: Bruno Wolff III||Date: 2003-06-28 03:27:29|
|Subject: Re: When will table partitioning be available..|
pgsql-general by date
|Next:||From: Ron Johnson||Date: 2003-06-28 03:50:58|
|Subject: Re: Redhat's "enhancements" to PG|
|Previous:||From: Tom Lane||Date: 2003-06-28 03:05:58|
|Subject: Re: dropping sequences |