diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-03 17:40:04 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-03 17:40:04 -0500 |
| commit | d4f4bdf23a47dc2b6122195bbff4b09c80e7e2f5 (patch) | |
| tree | b568774353603665d2900a8afeda81bc6f3fd36d /src/tutorial/funcs.c | |
| parent | bf63c4a29503c5817f96d77af83bf1f191fa42e3 (diff) | |
| download | postgresql-d4f4bdf23a47dc2b6122195bbff4b09c80e7e2f5.tar.gz postgresql-d4f4bdf23a47dc2b6122195bbff4b09c80e7e2f5.zip | |
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.
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions