08006 Connection Failure

If you encounter an error message like following.

LOG: could not receive data from client: Connection reset by peer

Although this log is emitted from Postgres, the cause for the error has nothing to do with the database itself. Your application happened to crash while connected to Postgres, and did not clean up its connection to the database. Postgres noticed that the client (your application) disappeared without ending the connection properly, and logged a message saying so.

If you are not seeing your application’s backtrace, you may need to ensure that you are, in fact, logging to stdout (instead of a file) and that you have stdout sync’d.

If you encounter an error message like following.

LOG: unexpected EOF on client connection with an open transaction

Although this log is emitted from Postgres, the cause for the error has nothing to do with the database itself. Your application happened to crash while connected to Postgres, and did not clean up its connection with an open transaction. Postgres noticed that the client (your application) disappeared without ending the connection properly, and logged a message saying so.

If you encounter an error message like following.

LOG: could not send data to client: Broken pipe

Although this log is emitted from Postgres, the cause for the error has nothing to do with the database itself. Your application happened to crash while connected to Postgres, and did not clean up its connection to the database. It is also possible that the network between the application and Postgres database is abnormally disconnected. Postgres noticed that the data could not be sent to the client because of a network anomaly, and logged a message saying so.