From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] freefuncs.c is never called from anywhere!? |
Date: | 2000-01-31 00:04:47 |
Message-ID: | 001101bf6b7e$c948b560$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-01-31 00:11:12 | Re: [HACKERS] Re: ORDBMS |
Previous Message | Hiroshi Inoue | 2000-01-30 23:41:55 | RE: ImmediateSharedRelationCacheInvalidate considered harmful |