]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1a70925) | patch
Volatile-ize all five places where we expect a PG_TRY block to restore
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 18 Feb 2010 23:50:20 +0000 (23:50 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 18 Feb 2010 23:50:20 +0000 (23:50 +0000)
commit08181b427c1b3a4537c331b30492da1881a5b341
tree8294f0b28edd0298464303912ea6e96f59b8080ftree | snapshot
parent1a709257a9f0b1e4c58f92e8efe934bc600656e4commit | diff
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.
src/pl/plpython/plpython.c diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git