You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this commit, the Client.end() method is changed
Before it calls connection.end() even after destroying the stream
Now if there's an active query, it only destroys the stream and not end the connection
We haven't been 100% sure this is the root cause, but I wonder if this is an intentional change. Logically it seems to make sense to close that connection no matter what. Would love your thoughts on this, let me know if I have any missing context, thanks a lot!
The text was updated successfully, but these errors were encountered:
Hello!
We're observing the following behavior on our servers:
ClientRead
This happens after we upgraded our
pg
from7.4.3
to8.3.0
. And the following code stands out, which might be the cause.3828aa86
In this commit, the
Client.end()
method is changedconnection.end()
even after destroying the streamWe haven't been 100% sure this is the root cause, but I wonder if this is an intentional change. Logically it seems to make sense to close that connection no matter what. Would love your thoughts on this, let me know if I have any missing context, thanks a lot!
The text was updated successfully, but these errors were encountered: