Re: Rare SSL failures on eelpout

Shawn Debnath <sdn@amazon.com>

From: Shawn Debnath <sdn@amazon.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-03-06T03:07:06Z
Lists: pgsql-hackers
On Wed, Mar 06, 2019 at 11:13:31AM +1300, Thomas Munro wrote:
> So... can anyone tell us what happens on Windows?

Voila!

C:\Users\Shawn Debnath\Desktop>systeminfo
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.17763 N/A Build 17763
[...]

C:\Users\Shawn Debnath\Desktop>c:\Python27\python.exe tmunro-ssl-test.py --server


C:\Users\Shawn Debnath\Desktop>c:\Python27\python.exe tmunro-ssl-test.py --client
Sending A...
2
Sending B...
[Errno 10054] An existing connection was forcibly closed by the remote host
Sending C...
[Errno 10054] An existing connection was forcibly closed by the remote host
Traceback (most recent call last):
  File "tmunro-ssl-test.py", line 57, in <module>
    client()
  File "tmunro-ssl-test.py", line 51, in client
    print s.recv(1024)
socket.error: [Errno 10054] An existing connection was forcibly closed by the remote host


-- 
Shawn Debnath
Amazon Web Services (AWS)


Commits

  1. Hack back-branch SSL tests to avoid intermittent buildfarm failures.

  2. Restructure libpq's handling of send failures.