Excerpts from Heikki Linnakangas's message of mar abr 26 15:06:51 -0300 2011:
> I tried to look around for other executor nodes that might
> have the same problem. I didn't see any obvious leaks, although index
> scan node seems to call AM's getnext without resetting the memory
> context in between. That's a pretty well-tested codepath, however, and
> there hasn't been any complains of leaks with index scans, so there must
> be something that mitigates it.
Don't we have some rule that functions used in index AMs are supposed to
be leak-free?
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
