aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-11 18:06:29 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-11 18:06:29 -0500
commit6fb17aeeab87dafca42a9db49ecb152a967d155c (patch)
tree804b16152188ae35832cd3a194240cbbd7958a8d /src/backend/access/gist
parentdd4e0a38781e0c48409f0c092b04b2ec75ed1a7e (diff)
downloadpostgresql-6fb17aeeab87dafca42a9db49ecb152a967d155c.tar.gz
postgresql-6fb17aeeab87dafca42a9db49ecb152a967d155c.zip
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
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions