diff options
| author | Bruce Momjian <bruce@momjian.us> | 2002-06-23 21:29:32 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2002-06-23 21:29:32 +0000 |
| commit | 5a151497368e2359065893b9ccce60e5357af9d0 (patch) | |
| tree | dee7e48b1f1f0b1211d46908dbc567cd7e0d7896 /src/backend/executor/nodeSubqueryscan.c | |
| parent | eb4e4fd2629e1ded5e88234935fe8705ee5ba6bf (diff) | |
| download | postgresql-5a151497368e2359065893b9ccce60e5357af9d0.tar.gz postgresql-5a151497368e2359065893b9ccce60e5357af9d0.zip | |
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
Diffstat (limited to 'src/backend/executor/nodeSubqueryscan.c')
0 files changed, 0 insertions, 0 deletions