Tom Lane writes:
> Applied, thanks. (Looks like the leaks were introduced fairly
> recently by the dynamic-search-path feature.)
Is there some sort of a system behind which places are subject to leaks
and which places are just too lazy to call pfree()?
I know that index support procedures must not leak, hmm, I guess this
would include the function manager...
(If that was not the right explanation, stop reading here.)
Why aren't index support procedures called with an appropriate memory
context set up? Since the functions currently do all the cleaning
themselves, couldn't it work like this:
1. set up memory context
2. call index procedure
3. clean out memory context
(This could even be slightly more efficient.)
Then again, I'm probably oversimplifying things...
--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter