From 46ee42b8162efe29bb38f07f694aafd992bcf4b1 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 6 Jul 2010 21:37:31 +0000
Subject: [PATCH] Add note that using PL/Python 2 and 3 in the same session
will probably crash
---
doc/src/sgml/plpython.sgml | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index 8b58a95a006..3f924e6cbf1 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.49 2010/03/29 21:35:59 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.50 2010/07/06 21:37:31 petere Exp $ -->
<chapter id="plpython">
<title>PL/Python - Python Procedural Language</title>
@@ -152,6 +152,15 @@
New In Python 3.0</ulink> for more information about porting to
Python 3.
</para>
+
+ <para>
+ On most (possibly all) platforms, it is not possible to use
+ PL/Python based on Python 2 and PL/Python based on Python 3 in the
+ same session, because the symbols in the dynamic modules will
+ clash, which will result in crashes of the PostgreSQL server
+ process. It is possible, however, to use both PL/Python variants
+ in the same database, from separate sessions.
+ </para>
</sect1>
<sect1 id="plpython-funcs">
--
GitLab