|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.48 2010/03/29 21:20:58 petere Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.49 2010/03/29 21:35:59 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="plpython">
|
4 | 4 | <title>PL/Python - Python Procedural Language</title>
|
|
27 | 27 |
|
28 | 28 | <para>
|
29 | 29 | As of <productname>PostgreSQL</productname> 7.4, PL/Python is only
|
30 |
| - available as an <quote>untrusted</> language (meaning it does not |
31 |
| - offer any way of restricting what users can do in it). It has |
| 30 | + available as an <quote>untrusted</> language,meaning it does not |
| 31 | + offer any way of restricting what users can do in it. It has |
32 | 32 | therefore been renamed to <literal>plpythonu</>. The trusted
|
33 | 33 | variant <literal>plpython</> might become available again in future,
|
34 |
| - if a new secure execution mechanism is developed in Python. |
| 34 | + if a new secure execution mechanism is developed in Python. The |
| 35 | + writer of a function in untrusted PL/Python must take care that the |
| 36 | + function cannot be used to do anything unwanted, since it will be |
| 37 | + able to do anything that could be done by a user logged in as the |
| 38 | + database administrator. Only superusers can create functions in |
| 39 | + untrusted languages such as <literal>plpythonu</literal>. |
35 | 40 | </para>
|
36 | 41 |
|
37 | 42 | <note>
|
|