|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/xplang.sgml,v 1.37 2010/04/03 07:22:56 petere Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/xplang.sgml,v 1.38 2010/05/30 02:23:09 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="xplang"> |
4 | 4 | <title>Procedural Languages</title> |
@@ -151,8 +151,10 @@ CREATE <optional>TRUSTED</optional> <optional>PROCEDURAL</optional> LANGUAGE <re |
151 | 151 | <optional>VALIDATOR <replaceable>validator_function_name</replaceable></optional> ; |
152 | 152 | </synopsis> |
153 | 153 | The optional key word <literal>TRUSTED</literal> specifies that |
154 | | - ordinary database users that have no superuser privileges should |
155 | | - be allowed to use this language to create functions and trigger |
| 154 | + the language does not grant access to data that the user would |
| 155 | + not otherwise have. Trusted languages are designed for ordinary |
| 156 | + database users (those without superuser privilege) and allows them |
| 157 | + to safely create of functions and trigger |
156 | 158 | procedures. Since PL functions are executed inside the database |
157 | 159 | server, the <literal>TRUSTED</literal> flag should only be given |
158 | 160 | for languages that do not allow access to database server |
|