From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Lars Kanis <lars(at)greiz-reinsdorf(dot)de> |
Subject: | Re: MSVC SSL test failure |
Date: | 2021-12-06 06:02:51 |
Message-ID: | 2998440.1638770571@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 12/5/21 12:50, Tom Lane wrote:
>> This looks quite a bit like the sort of failure that commit
>> 6051857fc was meant to forestall. I wonder whether reverting
>> that commit changes the results? You might also try inserting
>> a shutdown() call, as we'd decided not to do [1].
> Commenting out the closesocket() worked.
Man, that's annoying. Apparently OpenSSL is doing something to
screw up the shutdown sequence. According to [1], the graceful
shutdown sequence will happen by default, but changing SO_LINGER
or SO_DONTLINGER can get you into abortive shutdown anyway.
Maybe they change one of those settings (why?)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-12-06 06:16:11 | Re: Alter all tables in schema owner fix |
Previous Message | Kyotaro Horiguchi | 2021-12-06 06:02:50 | Re: Allow escape in application_name |