| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
| Cc: | "Alexandr" <AVShutko(at)mail(dot)khstu(dot)ru>, pgsql-bugs(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Postgres bug (working with iserverd) |
| Date: | 2001-05-15 05:17:34 |
| Message-ID: | 29814.989903854@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> writes:
>> However, EvalPlanQual still leaks more memory than suits me ---
>> auxiliary memory allocated by the plan nodes is not recovered.
> Isn't plan shutdown supposed to free memory?
Yeah, but it leaks all over the place; none of the plan node types
bother to free their state nodes, for example. There are lots of other
cases. You really have to reset the per-query context to get rid of all
the cruft allocated during ExecInitNode.
> How subselects run queries again and again?
They don't end and restart them; they just rescan them. If we had
this substitute-a-new-tuple hack integrated into the Param mechanism,
then EvalPlanQual could use ExecReScan too, but at the moment no...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul McGarry | 2001-05-15 06:47:30 | RE: Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1 |
| Previous Message | Paul McGarry | 2001-05-15 05:08:07 | Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-15 05:26:33 | Re: SCHEMA idea |
| Previous Message | Stephan Szabo | 2001-05-15 05:12:16 | Re: optimiser problem |