pgsql: Avoid "variable might be clobbered by longjmp" warning.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid "variable might be clobbered by longjmp" warning.
Date: 2013-03-28 17:19:56
Message-ID: E1ULGUW-0005yl-8g@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid "variable might be clobbered by longjmp" warning.

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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/58bc48179b3cad0793ae20b002d60289c8bf0b9b

Modified Files
--------------
src/backend/tcop/utility.c | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-03-28 19:26:33 pgsql: Update time zone data files to tzdata release 2013b.
Previous Message Alvaro Herrera 2013-03-28 16:08:30 pgsql: Add sql_drop event for event triggers