database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00
Code Activity

Install safeguard against running PL/Python 2 and 3 in the same session

Browse Source
This commit is contained in:
Peter Eisentraut
2010-07-08 18:42:12 +00:00
parent c9b142d965
commit 803716013d
2 changed files with 26 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/plpython.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.50 2010/07/06 21:37:31 petere Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.51 2010/07/08 18:42:12 petere Exp $ -->
<chapter id="plpython">
<title>PL/Python - Python Procedural Language</title>
@ -154,12 +154,13 @@
</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.
It is not allowed 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 would clash, which could result in crashes of the
PostgreSQL server process. There is a check that prevents mixing
Python major versions in a session, which will abort the session if
a mismatch is detected. It is possible, however, to use both
PL/Python variants in the same database, from separate sessions.
</para>
</sect1>