Re: [HACKERS] Fix for segfault in plpython's exception handling - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Fix for segfault in plpython's exception handling
Date
Msg-id 17995.1481299107@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] Fix for segfault in plpython's exception handling  (Rafa de la Torre <rtorre@carto.com>)
Responses Re: [HACKERS] Fix for segfault in plpython's exception handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Rafa de la Torre <rtorre@carto.com> writes:
>          exc = PyErr_NewException(exception_map[i].name, base, dict);
> +        Py_INCREF(exc);
>          PyModule_AddObject(mod, exception_map[i].classname, exc);

Hm.  Seems like if this is a problem, the code for the other three
exceptions is being a bit careless: it does do Py_INCREFs on them,
but not soon enough to ensure no problems.  Also, I wonder why that
code checks for a null result from PyErr_NewException but this doesn't.

Good catch though.  A naive person would have assumed that
PyModule_AddObject would increment the object's refcount, but
the Python docs say "This steals a reference to value", which
I guess must mean that the caller is required to do it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] jsonb problematic operators
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Logical Replication WIP