On 2023-11-27 Mo 07:39, Andrew Dunstan wrote:
>
> On 2023-11-27 Mo 07:00, Alexander Lakhin wrote:
>> Hello Kuroda-san,
>>
>> 25.11.2023 18:19, Hayato Kuroda (Fujitsu) wrote:
>>> Thanks for attaching a program. This helps us to understand the issue.
>>> I wanted to confirm your env - this failure was occurred on windows
>>> server XXXX, right?
>>
>> I see that behavior on:
>> Windows 10 Version 1607 (OS Build 14393.0)
>> Windows Server 2016 Version 1607 (OS Build 14393.0)
>> Windows Server 2019 Version 1809 (OS Build 17763.1)
>>
>> But it's not reproduced on:
>> Windows 10 Version 1809 (OS Build 17763.1) (triple-checked)
>> Windows Server 2019 Version 1809 (OS Build 17763.592)
>> Windows 10 Version 22H2 (OS Build 19045.3693)
>> Windows 11 Version 21H2 (OS Build 22000.613)
>>
>> So it looks like the failure occurs depending not on Windows edition,
>> but
>> rather on it's build. For Windows Server 2019 the "good" build is
>> somewhere between 17763.1 and 17763.592, but for Windows 10 it's between
>> 14393.0 and 17763.1.
>> (Maybe there was some change related to
>> FILE_DISPOSITION_POSIX_SEMANTICS/
>> FILE_DISPOSITION_ON_CLOSE implementation; I don't know where to find
>> information about that change.)
>>
>> It's also interesting, what is full version/build of OS on drongo and
>> fairywren.
>>
>>
>
> It's WS 2019 1809/17763.4252. The latest available AFAICT is 17763.5122
>
>
>
I've updated it to 17763.5122 now.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com