pgsql: Fix volatile vs. pointer confusion - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Fix volatile vs. pointer confusion
Date
Msg-id E1h4L4t-0002Z4-Cj@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix volatile vs. pointer confusion

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1226d932b4dadc39ba2f9a488e4d784443ea6a78

Modified Files
--------------
contrib/hstore_plpython/hstore_plpython.c | 9 ++++-----
contrib/jsonb_plpython/jsonb_plpython.c   | 9 +++------
2 files changed, 7 insertions(+), 11 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix thinko when bumping on temporary directories inpg_verify_ch
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Refactor ParamListInfo initialization