> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>
> "Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> > As far as I see,freeObject() has a fundamental problem.
> > Probably it couldn't free multiple references safely.
>
> Yes, that code will have a problem with node trees that have
> circular references or multiple links to the same node.
> Both of which are cases that we can currently generate :-(.
>
> Of course, circular links will also break copyfuncs, equalfuncs,
> and printfuncs. We have a known bug with the backend crashing
> when -d is enabled for certain queries, because of infinite
> recursion in printfuncs.
>
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() ?
Regards.
Hiroshi Inoue
Inoue@tpf.co.jp
