psycopg: SSL SYSCALL error: EOF detected
Hello,
English is not my native language so sorry for the mistakes
In general, the problem is as follows:
When I deploy the application, after a few hours it shuts down the connection with postgres and writes it in the logs
psycopg library, how can this be fixed?
7 Replies
Project ID:
1a4094a5-8dec-4ed3-a791-e7ddfc8cbd081a4094a5-8dec-4ed3-a791-e7ddfc8cbd08
this can usually happen when you are keeping connections open, postgres closes the connection but the client doesn't know the connection was closed
And how to keep them open? Or do I need to initialize a new connection every few hours?
unfortunately I don't have an exact answer to that, it's something you would have to reference the client libraries documentation for
When I hadn't upgraded to version 2 yet, it always worked fine. Maybe that's the point? Or is it possible to do something on the server so that it does not reset the connection?
no sorry this isnt an issue with postgres or railway, its how your database client is handling closed connections, or should i say, not handling closed connections