diff options
| author | Tom Lane | 2011-03-07 02:15:48 +0000 |
|---|---|---|
| committer | Tom Lane | 2011-03-07 02:15:48 +0000 |
| commit | 4172bd88300524efd1728c247fbc1eff3c1ca6ed (patch) | |
| tree | 3fb12ae1435f980a6743af4c52d33718f2810d9a /src/pl/plpython/plpython.c | |
| parent | dfe18f18d262df731378cbf38a4136f08ca119a5 (diff) | |
Suppress some "variable might be clobbered by longjmp" warnings.
Seen with an older gcc version. I'm not sure these represent any real
risk factor, but still a bit scary. Anyway we have lots of other
volatile-marked variables in this code, so a couple more won't hurt.
Diffstat (limited to 'src/pl/plpython/plpython.c')
| -rw-r--r-- | src/pl/plpython/plpython.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/pl/plpython/plpython.c b/src/pl/plpython/plpython.c index e415aa36f41..4a9e2a4f181 100644 --- a/src/pl/plpython/plpython.c +++ b/src/pl/plpython/plpython.c @@ -1516,7 +1516,7 @@ static PLyProcedure * PLy_procedure_get(Oid fn_oid, bool is_trigger) { HeapTuple procTup; - PLyProcedureEntry *entry; + PLyProcedureEntry * volatile entry; bool found; procTup = SearchSysCache1(PROCOID, ObjectIdGetDatum(fn_oid)); @@ -3234,7 +3234,7 @@ PLy_spi_prepare(PyObject *self, PyObject *args) void *tmpplan; volatile MemoryContext oldcontext; volatile ResourceOwner oldowner; - int nargs; + volatile int nargs; if (!PyArg_ParseTuple(args, "s|O", &query, &list)) return NULL; @@ -3470,7 +3470,7 @@ PLy_spi_execute_plan(PyObject *ob, PyObject *list, long limit) PG_TRY(); { - char *nulls; + char * volatile nulls; volatile int j; if (nargs > 0) |