Fix memory leaks in custom executor #256
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.
When one calls
elog(ERROR,...
itlongjmp
out of the current stack leaving no chance for the C++ to be executed.This PR is a first iteration toward what we want to rationalize (cf. #93 ):
This fixes #120, even though there still seem to be a small leak with DuckDB's
PrepareQuery
leftover (to be followed-up separately)