| From: | momjian(at)postgresql(dot)org (Bruce Momjian - CVS) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql/src/backend/executor nodeIndexscan.c |
| Date: | 2002-06-23 21:29:32 |
| Message-ID: | 20020623212932.AC295475DE7@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql
Changes by: momjian(at)postgresql(dot)org 02/06/23 17:29:32
Modified files:
src/backend/executor: nodeIndexscan.c
Log message:
It seems that ExecInit/EndIndexScan is leaking some memory...
For example, if I run a query, that uses an index scan, and call
MemoryContextSt ats (CurrentMemoryContext) before ExecutorStart() and
after ExecutorEnd() in ProcessQuery(), I am consistently see ing that
the 'after' call shows 256 bytes more used, then 'before'...
The problem seems to be in ExecEndIndexScan - it does not release
scanstate, ind exstate, indexstate->iss_RelationDescs and indexstate ->
iss_ScanDescs...
Dmitry Tkach
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian - CVS | 2002-06-23 21:40:52 | pgsql/contrib/dbmirror |
| Previous Message | Bruce Momjian - CVS | 2002-06-23 21:20:38 | pgsql/contrib/isbn_issn isbn_issn.sql.in |