postgresql/src/backend/access
Tom Lane 2b78d101d1 Fix SQL function execution to be safe with long-lived FmgrInfos.
fmgr_sql had been designed on the assumption that the FmgrInfo it's called
with has only query lifespan.  This is demonstrably unsafe in connection
with range types, as shown in bug #7881 from Andrew Gierth.  Fix things
so that we re-generate the function's cache data if the (sub)transaction
it was made in is no longer active.

Back-patch to 9.2.  This might be needed further back, but it's not clear
whether the case can realistically arise without range types, so for now
I'll desist from back-patching further.
2013-03-03 17:39:58 -05:00
..
common Improve concurrency of foreign key locking 2013-01-23 12:04:59 -03:00
gin Update copyrights for 2013 2013-01-01 17:15:01 -05:00
gist Support unlogged GiST index. 2013-02-11 23:07:09 +02:00
hash Provide database object names as separate fields in error messages. 2013-01-29 17:08:26 -05:00
heap Fix Xmax freeze conditions 2013-02-08 12:50:58 -03:00
index Update copyrights for 2013 2013-01-01 17:15:01 -05:00
nbtree Provide database object names as separate fields in error messages. 2013-01-29 17:08:26 -05:00
rmgrdesc Move relpath() to libpgcommon 2013-02-21 22:46:17 -03:00
spgist Update copyrights for 2013 2013-01-01 17:15:01 -05:00
transam Fix SQL function execution to be safe with long-lived FmgrInfos. 2013-03-03 17:39:58 -05:00
Makefile Split out rmgr rm_desc functions into their own files 2012-11-28 13:01:15 -03:00