| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: freefuncs.c is never called from anywhere!? |
| Date: | 2000-06-09 18:14:14 |
| Message-ID: | Pine.LNX.3.96.1000609201103.8392A-100000@ara.zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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...
No. I mean _common_ for manipulation with query/plan tree.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-06-09 18:39:19 | Re: freefuncs.c is never called from anywhere!?] |
| Previous Message | Tom Lane | 2000-06-09 17:53:29 | Re: libpq problems in CVS |