Fix memory leak when executing vectorized quals #242
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, a
VectorColumn
structure is created when executing vectorized quals for each tuple on the ExecutorState memory context. However, it will be freed only until execution finishes. This commit changes the memory context to a tuple memory context.Here are steps to reproduce:
git clone https://github.com/gregrahn/tpch-kit.git cd tpch-kit/dbgen
Make sure the following in Makefie:
psql
;top
to monitor the memory used by the backend process;In the
top
you will see the memory increased and finally cause out of memory.