Message-ID: <4542bf4e-9eae-9622-e351-ee96b48f05df@postgrespro.ru>
Date: Fri, 14 Jan 2022 15:15:05 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.5.0
Subject: Re: Windows: Wrong error message at connection termination
Content-Language: en-US
From: Sergey Shinderuk <s.shinderuk@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>, Alexander Lakhin <exclusion@gmail.com>
Cc: Lars Kanis <lars@greiz-reinsdorf.de>,
 Thomas Munro <thomas.munro@gmail.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <90b34057-4176-7bb0-0dbb-9822a5f6425b@greiz-reinsdorf.de>
 <CA+hUKG+nzfwuKYKXd43jjG2txuc-po4GOyZFA3z6s9oy3P=4kA@mail.gmail.com>
 <2858709.1637201040@sss.pgh.pa.us>
 <6dad5499-ced4-ac82-4f5d-fb6311378176@greiz-reinsdorf.de>
 <CA+hUKGJ7-Hm3jsK5WWgoMJfuQM9EVwQvjRYqbgLPKzJb0i_LvA@mail.gmail.com>
 <CA+hUKGKjXEE-cZPt8QuR2y_8eATRaiNDbQ6MXQ0SrdFikw=8bw@mail.gmail.com>
 <3616081.1637530966@sss.pgh.pa.us>
 <CA+hUKG+HGEb=ED9RHZ6UCwOFNffk9NqkRJRGVy+AA-T4yGYodg@mail.gmail.com>
 <3627376.1637535867@sss.pgh.pa.us>
 <cfd25a75-7856-0dc4-bba0-49216cb135a9@greiz-reinsdorf.de>
 <d5e763b6-c9ef-036f-1ced-653926d3875c@gmail.com>
 <1283317.1638213407@sss.pgh.pa.us>
 <3a497c66-6685-c1c1-1eb4-1636e9ac5442@gmail.com>
 <2120381.1638473504@sss.pgh.pa.us>
 <c093f68b-be35-df40-b2fd-e0b167bddf4f@postgrespro.ru>
In-Reply-To: <c093f68b-be35-df40-b2fd-e0b167bddf4f@postgrespro.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/4542bf4e-9eae-9622-e351-ee96b48f05df%40postgrespro.ru>
Precedence: bulk

On 14.01.2022 13:01, Sergey Shinderuk wrote:
> When the timeout expires, the server sends the error message and 
> gracefully closes the connection by sending a FIN.  Later, psql sends 
> another query to the server, and the server responds with a RST.  But 
> now recv() returns WSAECONNABORTED(10053) instead of WSAECONNRESET(10054).

On the other hand, I cannot reproduce this behavior with a remote server 
even if pause psql just before the recv() call to let the RST win the race.

So I get:

postgres=# set idle_session_timeout = '1s';
recv() returned 15 errno 0
SET
recv() returned -1 errno 10035 (WSAEWOULDBLOCK)
postgres=# select 1;
recv() returned 116 errno 0
recv() returned 0 errno 0
recv() returned 0 errno 0
FATAL:  terminating connection due to idle-session timeout
server closed the connection unexpectedly
         This probably means the server terminated abnormally
         before or while processing the request.

recv() signals EOF like on Unix.

Here I connected from a Windows virtual machine to the macOS host, but 
the Wireshark dump looks the same (there is a RST) as for a localhost 
connection.

Is this "error-eating" behavior of RST on Windows specific only to 
localhost connections?

-- 
Sergey Shinderuk		https://postgrespro.com/