fix: Connection timeout handling for native clients in connected state#3512
Merged
brianc merged 1 commit intobrianc:masterfrom Feb 3, 2026
Merged
Conversation
Now, when using the native client with a connection timeout, the pool could incorrectly destroy or end a client that was already connected, due to not distinguishing between connection states. This caused issues such as brianc/node-pg-native#49, where a native client that had already established a connection could be forcefully closed if the connection callback was delayed past the timeout.
maxbronnikov10
force-pushed
the
fix/native-client-connect-timeout
branch
from
5923484 to
8206f7a
Compare
Contributor
Author
|
@brianc Hello! Sry for tag. Can u check PR pls? |
Contributor
Author
|
or maybe @charmander can check pls? |
Contributor
Author
|
@charmander @brianc Hello! Can u check PR pls |
1 similar comment
Contributor
Author
|
@charmander @brianc Hello! Can u check PR pls |
Owner
|
Thanks! Super sorry I missed this. It looks good to me! |
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.
Now, when using the native client with a connection timeout, the pool could incorrectly destroy or end a client that was already connected, due to not distinguishing between connection states. This caused issues such as brianc/node-pg-native#49, where a native client that had already established a connection could be forcefully closed if the connection callback was delayed past the timeout.