Skip site navigation (1) Skip section navigation (2)

pgsql: Volatile-ize all five places where we expect a PG_TRY block to

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Volatile-ize all five places where we expect a PG_TRY block to
Date: 2010-02-18 23:50:27
Message-ID: 20100218235027.305BE7541C5@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Volatile-ize all five places where we expect a PG_TRY block to restore
old memory context in plpython.  Before only one of them was marked
volatile, but per report from Zdenek Kotala, some compilers do the
wrong thing here.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/pl/plpython:
        plpython.c (r1.90.2.5 -> r1.90.2.6)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.90.2.5&r2=1.90.2.6)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-02-18 23:50:33
Subject: pgsql: Volatile-ize all five places where we expect a PG_TRY block to
Previous:From: Tom LaneDate: 2010-02-18 23:50:20
Subject: pgsql: Volatile-ize all five places where we expect a PG_TRY block to

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group