Fix I/O-conversion-related memory leaks in plpgsql.
Datatype I/O functions are allowed to leak memory in CurrentMemoryContext,
since they are generally called in short-lived contexts. However, plpgsql
calls such functions for purposes of type conversion, and was calling them
in its procedure context. Therefore, any leaked memory would not be
recovered until the end of the plpgsql function. If such a conversion
was done within a loop, quite a bit of memory could get consumed. Fix by
calling such functions in the transient "eval_econtext", and adjust other
logic to match. Back-patch to all supported versions.
Andres Freund, Jan Urbański, Tom Lane
Branch
------
REL8_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/3eb2ff16db00bb1d2bc73a263766b7224e810321
Modified Files
--------------
src/pl/plpgsql/src/pl_exec.c | 169 +++++++++++++++++++++++++----------------
1 files changed, 103 insertions(+), 66 deletions(-)
