Add some information about what it means for PL/Python to be untrusted.

Similar information already appears in the PL/Perl and PL/Tcl chapters.

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index ab9ad2228af95fc42ed3fe7b4ca6353c71787d9e..8b58a95a006f752b66e9df616049df57795408a3 100644 (file)
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  PL/Python - Python Procedural Language
@@ -27,11 +27,16 @@
 
  
   As of PostgreSQL 7.4, PL/Python is only
-  available as an untrusted language (meaning it does not
-  offer any way of restricting what users can do in it).  It has
+  available as an untrusted language, meaning it does not
+  offer any way of restricting what users can do in it.  It has
   therefore been renamed to plpythonu.  The trusted
   variant plpython might become available again in future,
-  if a new secure execution mechanism is developed in Python.
+  if a new secure execution mechanism is developed in Python.  The
+  writer of a function in untrusted PL/Python must take care that the
+  function cannot be used to do anything unwanted, since it will be
+  able to do anything that could be done by a user logged in as the
+  database administrator.  Only superusers can create functions in
+  untrusted languages such as plpythonu.