Re: Windows: Wrong error message at connection termination
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergey Shinderuk <s.shinderuk@postgrespro.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
Alexander Lakhin <exclusion@gmail.com>,
Lars Kanis <lars@greiz-reinsdorf.de>,
Thomas Munro <thomas.munro@gmail.com>
Date: 2022-01-15T18:58:46Z
Lists: pgsql-hackers
Sergey Shinderuk <s.shinderuk@postgrespro.ru> writes: > On 14.01.2022 13:01, Sergey Shinderuk wrote: >> Unexpectedly, this changes the error message: > ... > For the record, after more poking I realized that it depends on timing. > By injecting delays I can get any of the following from libpq: > * could not receive data from server: Software caused connection abort > * server closed the connection unexpectedly > * no connection to the server Thanks for the follow-up. At the moment I'm not planning to do anything pending the results of the other thread [1]. It seems likely though that we'll end up reverting this explicit-close behavior in the back branches, as the other changes involved look too invasive for back-patching. regards, tom lane [1] https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BOeoETZQ%3DQw5Ub5h3tmwQhBmDA%3DnuNO3KG%3DzWfUypFAw%40mail.gmail.com
Commits
-
On Windows, close the client socket explicitly during backend shutdown.
- 00cd81723cd0 10.20 landed
- a87c8c3edd7f 11.15 landed
- 3e644dcca1e9 12.10 landed
- 6251f86241ac 13.6 landed
- 4cd2928543c1 14.2 landed
- 6051857fc953 15.0 landed