diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-03 17:39:58 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-03 17:39:58 -0500 |
| commit | 2b78d101d1d6b1d8533a7b7aeff4d82b10a915f8 (patch) | |
| tree | 72f853c8e4b9cf21b5c24eb0eb4481b067f36e89 /src/bin/psql/tab-complete.c | |
| parent | 891869c352160e480d4afdc2a3443035c2560282 (diff) | |
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/bin/psql/tab-complete.c')
0 files changed, 0 insertions, 0 deletions