pgsql: Fix volatile vs. pointer confusion

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix volatile vs. pointer confusion
Date: 2019-03-15 07:59:51
Message-ID: E1h4hkt-0006Nu-HX@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a1e9508b964155a81ec9a8e6e12be76796d47097

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

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2019-03-15 09:34:17 pgsql: Add walreceiver API to get remote server version
Previous Message Michael Paquier 2019-03-15 07:22:14 pgsql: Fix typo related to to_tsvector() in tests of json and jsonb