Marko Kreen <marko@l-t.ee> writes:
> Look at the attached Python script, it reproduces the problem.
Hmm. You'd probably have much better luck if you rewrote the check_code
function in plpgsql: that should eliminate the memory-leak problem, and
also speed things up because plpgsql knows about caching query plans
across function calls. IIRC, sql functions don't do that.
The memory leakage is definitely a bug, but not one that is going to get
fixed for 7.2. It'll take some nontrivial work on the SQL function
executor...
regards, tom lane