Fix PostgreSQL memory leak when statement cache is disabled#4337
Open
deathlesz wants to merge 2 commits into
Open
Fix PostgreSQL memory leak when statement cache is disabled#4337deathlesz wants to merge 2 commits into
deathlesz wants to merge 2 commits into
Conversation
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
1 participant
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.
Does your PR solve an issue?
Fixes:
Is this a breaking change?
No, don't think so.
This change only affects the case where the statement cache is disabled. Previously, named prepared statements were created that were never cached or closed, causing them to accumulate on the server. With this fix unnamed statements are used instead, preventing the leak without changing query results.