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
Is there any way to achieve a max connection lifetime in the pool, even for active connections? We're running this in a network with firewalls that kills connections after 1 hour regardless of how active they are. We're seeing a lot of errors in pooler because of closed socket:
Or, alternatively, is there a way for pooler or epgsql to handle that message and self-close the connection process when the socket is closed remotely?
The text was updated successfully, but these errors were encountered:
Is there any way to achieve a max connection lifetime in the pool, even for active connections? We're running this in a network with firewalls that kills connections after 1 hour regardless of how active they are. We're seeing a lot of errors in
pooler
because of closed socket:Or, alternatively, is there a way for
pooler
orepgsql
to handle that message and self-close the connection process when the socket is closed remotely?The text was updated successfully, but these errors were encountered: