Demonitor on Parameters delete to stop monitor leak#781
Merged
josevalim merged 1 commit intoJul 10, 2026
Conversation
ribanez7
force-pushed
the
fix/parameters-demonitor-leak
branch
from
9db6e92 to
edfd87f
Compare
ribanez7
force-pushed
the
fix/parameters-demonitor-leak
branch
from
edfd87f to
3d1038d
Compare
Member
|
💚 💙 💜 💛 ❤️ |
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.
Fixes #780.
Postgrex.Parametersmonitors on insert but never demonitors on delete, so every in-place reconnect leaks a monitor. This adds theProcess.demonitor(ref, [:flush])already used in the other monitoring modules.