Re: Progress report: intraquery memory recovery in executor - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Progress report: intraquery memory recovery in executor
Date
Msg-id 200007101317.JAA26491@candle.pha.pa.us
Whole thread Raw
In response to Progress report: intraquery memory recovery in executor  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Progress report: intraquery memory recovery in executor  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: postmaster errors with index on temp table?
Next
From: Philip Warner
Date:
Subject: Re: postmaster errors with index on temp table?