database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-11 20:28:21 +03:00
Code Activity

Fix volatile vs. pointer confusion

Browse Source 
Variables used after a longjmp() need to be declared volatile.  In
case of a pointer, it's the pointer itself that needs to be declared
volatile, not the pointed-to value.  So we need

    PyObject *volatile items;

instead of

    volatile PyObject *items;  /* wrong */

Discussion: https://www.postgresql.org/message-id/flat/f747368d-9e1a-c46a-ac76-3c27da32e8e4%402ndquadrant.com
This commit is contained in:
Peter Eisentraut
2019-03-14 08:25:25 +01:00
parent 6eebfdc38b
commit 1226d932b4
2 changed files with 7 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
contrib/jsonb_plpython/jsonb_plpython.c
View File

@ -237,17 +237,14 @@ PLyMapping_ToJsonbValue(PyObject *obj, JsonbParseState **jsonb_state)
JsonbValue *out = NULL;
/* We need it volatile, since we use it after longjmp */
volatile PyObject *items_v = NULL;
PyObject *volatile items = NULL;
pcount = PyMapping_Size(obj);
items_v = PyMapping_Items(obj);
items = PyMapping_Items(obj);
PG_TRY();
{
Py_ssize_t i;
PyObject *items;
items = (PyObject *) items_v;
pushJsonbValue(jsonb_state, WJB_BEGIN_OBJECT, NULL);
@ -279,7 +276,7 @@ PLyMapping_ToJsonbValue(PyObject *obj, JsonbParseState **jsonb_state)
}
PG_CATCH();
{
Py_DECREF(items_v);
Py_DECREF(items);
PG_RE_THROW();
}
PG_END_TRY();