| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | pgsql-hackers(at)postgreSQL(dot)org | 
| Subject: | Re: Progress report: intraquery memory recovery in executor | 
| Date: | 2000-07-10 13:17:57 | 
| Message-ID: | 200007101317.JAA26491@candle.pha.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
> What I'm currently considering instead is to still create a per-tuple
> context for each plan node, but use it only for expression evaluation,
> ie, we switch into it on entry to ExecQual(), ExecTargetList(),
> ExecProject(), maybe a few other places.  The majority of our leakage
> problems are associated with expression evaluation, so this should allow
> fixing the leakage problems.  It will mean that routines associated with
> plan nodes (basically, executor/node*.c) will still need to be careful
> to avoid leaks.  For the most part they are already, but I had hoped to
> make that care less necessary.
I was wondering how you were going to pull this off.  It seems doing
something on entry to the expression routines is best.
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-07-10 13:21:46 | Re: postmaster errors with index on temp table? | 
| Previous Message | Bruce Momjian | 2000-07-10 13:15:34 | Re: postmaster errors with index on temp table? |