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

Commit12bf602

Browse files
committed
Add a comment explaining the recent fix for plpython breakage in commit4c966d9.
Mostly text supplied by Jan Urbański.
1 parent908ab80 commit12bf602

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

‎src/pl/plpython/plpython.c

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3936,6 +3936,16 @@ PLy_add_exceptions(PyObject *plpy)
39363936
#endif
39373937
if (PyModule_AddObject(plpy,"spiexceptions",excmod)<0)
39383938
PLy_elog(ERROR,"failed to add the spiexceptions module");
3939+
3940+
/*
3941+
* XXX it appears that in some circumstances the reference count of the
3942+
* spiexceptions module drops to zero causing a Python assert failure when
3943+
* the garbage collector visits the module. This has been observed on the
3944+
* buildfarm. To fix this, add an additional ref for the module here.
3945+
*
3946+
* This shouldn't cause a memory leak - we don't want this garbage collected,
3947+
* and this function shouldn't be called more than once per backend.
3948+
*/
39393949
Py_INCREF(excmod);
39403950

39413951
PLy_exc_error=PyErr_NewException("plpy.Error",NULL,NULL);

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp