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

From Peter Eisentraut
Subject pgsql: Fix volatile vs. pointer confusion
Date
Msg-id E1h4hkt-0006Ny-I3@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
------
REL9_6_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/626c8ed2ef6dbca7df7d445875d133638b360dd1

Modified Files
--------------
contrib/hstore_plpython/hstore_plpython.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix typo related to to_tsvector() in tests of json and jsonb
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Add walreceiver API to get remote server version