Skip site navigation (1) Skip section navigation (2)

RE: [HACKERS] freefuncs.c is never called from anywhere!?

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 (view raw or flat)
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

In response to

Responses

pgsql-hackers by date

Next:From: Chris BitmeadDate: 2000-01-31 00:11:12
Subject: Re: [HACKERS] Re: ORDBMS
Previous:From: Hiroshi InoueDate: 2000-01-30 23:41:55
Subject: RE: ImmediateSharedRelationCacheInvalidate considered harmful

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group