From e8fc0f70c4bb0bdcff8edc748ae7e04a0fcbf7b4 Mon Sep 17 00:00:00 2001 From: vignesh Date: Wed, 29 Jan 2020 16:23:51 +0530 Subject: [PATCH] Doc update for the server message not being displayed when the client connection is closed by the server. Doc update for the server message not being displayed when the client connection is closed by the server in case of idle_in_transaction_session_timeout, pg_terminate_backend, pg_ctl kill TERM and drop database with (force). When the server closes client connection, it sends the ErrorResponse packet, and then closes the socket and terminates the backend process. If the packet is received before the server closes the connection, the error message is received in both windows and linux. If the packet is not received before the server closes the connection, the error message is not received in case of windows where as in non-windows it is received. --- doc/src/sgml/runtime.sgml | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index a34d31d..3a0abd7 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -627,6 +627,36 @@ psql: could not connect to server: No such file or directory indicate more fundamental problems, like lack of network connectivity. + + + You will get server closed the connection unexpectedly message while + trying to execute sql command on disconnected connection. The message is + slightly different in windows and non-windows. In non-windows, you will + see a FATAL message before the error message: + +FATAL: terminating connection due to idle-in-transaction timeout +server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. +The connection to the server was lost. Attempting reset: Succeeded. + + In windows, you might not see the FATAL message: + +server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. +The connection to the server was lost. Attempting reset: Succeeded. + + This message "FATAL: terminating connection due to idle-in-transaction + timeout" that is sent from server will not be displayed in windows, + however it will be present in the log file. The reason for this is, in + windows the client cannot receive the message sent by the server when the + server has closed the client connection. This behavior can be noticed when + the client connection has been disconnected because of + idle_in_transaction_session_timeout, pg_terminate_backend, pg_ctl kill + TERM and drop database with (force). + + -- 1.8.3.1