fix(db-postgres): release connection back to pool in connectWithReconnect#16893
Open
deepshekhardas wants to merge 1 commit into
Open
fix(db-postgres): release connection back to pool in connectWithReconnect#16893deepshekhardas wants to merge 1 commit into
deepshekhardas wants to merge 1 commit into
Conversation
1 task
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
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.
Description
The \connectWithReconnect\ function calls \pool.connect()\ to check out a client from the connection pool, attaches an error listener to detect ECONNRESET errors, but never calls
esult.release()\ to return the client back to the pool.
This results in a connection leak where every invocation permanently holds a connection from the pool, eventually causing pool exhaustion.
Fix
Added
esult.release()\ after attaching the error listener. The listener remains active on the pooled connection, so ECONNRESET detection still works when the connection is checked out for actual queries.
Fixes #16772 (connection leak portion)