From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 13:38:23 |
Message-ID: | 2E608EBA-F707-4DEC-B626-2FA7F6DE1A1B@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 6 Dec 2021, at 07:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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?)
AFAICT they don't touch either, and nothing really sticks out looking at
setsockopt calls in either 1.1.1 or 3.0.0.
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Nitin Jadhav | 2021-12-06 13:58:26 | Re: Multi-Column List Partitioning |
Previous Message | Justin Pryzby | 2021-12-06 13:36:55 | Re: GUC flags |