]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: eb4e4fd) | patch
It seems that ExecInit/EndIndexScan is leaking some memory...
authorBruce Momjian <bruce@momjian.us>
Sun, 23 Jun 2002 21:29:32 +0000 (21:29 +0000)
committerBruce Momjian <bruce@momjian.us>
Sun, 23 Jun 2002 21:29:32 +0000 (21:29 +0000)
commit5a151497368e2359065893b9ccce60e5357af9d0
treedee7e48b1f1f0b1211d46908dbc567cd7e0d7896tree | snapshot
parenteb4e4fd2629e1ded5e88234935fe8705ee5ba6bfcommit | diff
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
src/backend/executor/nodeIndexscan.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.