Conversation
theory
force-pushed
the
memleaks
branch
2 times, most recently
from
0268fc2 to
5b253c7
Compare
serprex
approved these changes
Jun 15, 2026
Collaborator
Author
|
Stupid GitHub, this was merged in 22d3c5d. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The Postgres memory context functions, including
AllocSetContextCreate(),palloc(), and friends, throw an error (longjmp) on error, leaving memory allocated by Curl living in the response object un-freed. Borrow thePG_TRY()pattern used byhttp_streaming_query()to catch these exceptions and free all the allocated memory. Resolves #274.