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
The PG pool opens connections towards the database. When the app is killed, or when a script finishes, these aren't gracefully terminated and we get these messages:
db_1 | 2019-03-12 12:55:42.030 UTC [9527] xxx@xxx LOG: could not receive data from client: Connection reset by peer
db_1 | 2019-03-12 12:55:42.030 UTC [9528] xxx@xxx LOG: could not receive data from client: Connection reset by peer
db_1 | 2019-03-12 12:55:42.033 UTC [9529] xxx@xxx LOG: could not receive data from client: Connection reset by peer
This isn't causing functional problems, but it's not ideal either.
There are other examples where we want to react to the termination of the program -- maybe stop accepting new requests and wait for active ones to finish?
What would be the correct way for the framework to support graceful shutdowns?
The text was updated successfully, but these errors were encountered:
The PG pool opens connections towards the database. When the app is killed, or when a script finishes, these aren't gracefully terminated and we get these messages:
This isn't causing functional problems, but it's not ideal either.
There are other examples where we want to react to the termination of the program -- maybe stop accepting new requests and wait for active ones to finish?
What would be the correct way for the framework to support graceful shutdowns?
The text was updated successfully, but these errors were encountered: