"Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> Multiple links to the same node is not so fatal for other xxxxObject().
> In fact they are used without big problem.
> But isn't it fatal for freeObject() ?
Yes, of course. We could possibly fix that by maintaining a list of
already-freed nodes during any one freeObject() call, but that seems
painful and slow.
However, the case I'm interested in would only be trying to free
nodetrees that were created by either copyObject or stringToNode,
and since neither of those routines produce multiple or circular
links, it seems safe enough to use freeObject as-is for the purpose.
regards, tom lane