database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-02 09:02:37 +03:00
Code Activity

Avoid "variable might be clobbered by longjmp" warning.

Browse Source 
On older-model gcc, the original coding of UTILITY_BEGIN_QUERY() can
draw this error because of multiple assignments to _needCleanup.
Rather than mark that variable volatile, we can suppress the warning
by arranging to have just one unconditional assignment before PG_TRY.
This commit is contained in:
Tom Lane
2013-03-28 13:19:49 -04:00
parent 473ab40c8b
commit 58bc48179b
1 changed files with 2 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/tcop/utility.c
View File

@ -380,12 +380,9 @@ ProcessUtility(Node *parsetree,
*/ */
#define UTILITY_BEGIN_QUERY(isComplete) \ #define UTILITY_BEGIN_QUERY(isComplete) \
do { \ do { \
bool _needCleanup = false; \ bool _needCleanup; \
\ \
if (isComplete) \ _needCleanup = (isComplete) && EventTriggerBeginCompleteQuery(); \
{ \
_needCleanup = EventTriggerBeginCompleteQuery(); \
} \
\ \
PG_TRY(); \ PG_TRY(); \
{ \ { \