Document which Python environment variables affect PL/Python

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index c76012db402ef732490d7b37463ac4d611b4318f..988234ce8a9b12cbe92fd8ae7959ae24d65ce84e 100644 (file)
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  PL/Python - Python Procedural Language
@@ -958,4 +958,64 @@ $$ LANGUAGE plpythonu;
   
  
 
+ 
+  Environment Variables
+
+  
+   Some of the environment variables that are accepted by the Python
+   interpreter can also be used to affect PL/Python behavior.  They
+   would need to be set in the environment of the main PostgreSQL
+   server process, for example in a start script.  The available
+   environment variables depend on the version of Python; see the
+   Python documentation for details.  At the time of this writing, the
+   following environment variables have an affect on PL/Python,
+   assuming an adequate Python version:
+   
+    
+     PYTHONHOME
+    
+
+    
+     PYTHONPATH
+    
+
+    
+     PYTHONY2K
+    
+
+    
+     PYTHONOPTIMIZE
+    
+
+    
+     PYTHONDEBUG
+    
+
+    
+     PYTHONVERBOSE
+    
+
+    
+     PYTHONCASEOK
+    
+
+    
+     PYTHONDONTWRITEBYTECODE
+    
+
+    
+     PYTHONIOENCODING
+    
+
+    
+     PYTHONUSERBASE
+    
+   
+
+   (It appears to be a Python implementation detail beyond the control
+   of PL/Python that some of the environment variables listed on
+   the python man page are only effective in a
+   command-line interpreter and not an embedded Python interpreter.)
+  
+