Re: freefuncs.c is never called from anywhere!?

Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
>> IIRC, some people were concerned about the fact that freeObject()
>> couldn't possibly cope with circular structures, multiply-linked
>> subexpressions, etc. I don't think that's a problem for my intended
>> use in the relcache --- the only structures I'll be freeing are ones
>> previously read in by the node-reading functions, and those aren't
>> going to have any surprises like that.

> IMHO use separate memory context will better and more fast way than
> freeObject().

A separate memory context for each relcache entry? I don't think so...
contexts aren't likely to be *that* cheap. Especially since I'd
probably need at least two contexts per relcache entry in order to do it
that way.

regards, tom lane