Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit46ee42b

Browse files
committed
Add note that using PL/Python 2 and 3 in the same session will probably crash
1 parent5acd417 commit46ee42b

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

‎doc/src/sgml/plpython.sgml

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.49 2010/03/29 21:35:59 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.50 2010/07/06 21:37:31 petere Exp $ -->
22

33
<chapter id="plpython">
44
<title>PL/Python - Python Procedural Language</title>
@@ -152,6 +152,15 @@
152152
New In Python 3.0</ulink> for more information about porting to
153153
Python 3.
154154
</para>
155+
156+
<para>
157+
On most (possibly all) platforms, it is not possible to use
158+
PL/Python based on Python 2 and PL/Python based on Python 3 in the
159+
same session, because the symbols in the dynamic modules will
160+
clash, which will result in crashes of the PostgreSQL server
161+
process. It is possible, however, to use both PL/Python variants
162+
in the same database, from separate sessions.
163+
</para>
155164
</sect1>
156165

157166
<sect1 id="plpython-funcs">

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp