On Tue, Dec 11, 2001 at 01:06:13PM -0500, Tom Lane wrote:
> 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.
And I thought that the 'sql' is the more lightweight approach...
Thanks, now it seems to work.
--
marko
