Emit a 'release' event when a connection is released back to the pool #2845
+38 −0
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.
This PR has the
Poolobject emit a'release'event upon the release of a client/connection back to the pool.We're experiencing an issue that feels quite similar to what's described in #2262, and in reading through the comments there, I was interested to see @brianc's suggestion of adding a
'release'event as the corresponding bookend to the'connect'and'acquire'events. However, in searching the code, it seems this was never implemented, so I've implemented that here.