Hi,
On 2023-05-05 07:08:39 -0400, Andrew Dunstan wrote:
> On 2023-05-04 Th 19:54, Andres Freund wrote:
> > Hm. I can't reproduce this in my test win10 VM, unfortunately. What OS / OS
> > version is the host? Any chance to get systeminfo.exe output or something
> > like
> > that?
>
>
> Its a Windows Server 2019 (v 1809) instance running on AWS.
Hm. When I hit the python issue I also couldn't repro it on windows 10. Cirrus
was also using Windows Server 2019...
> > I think we ought to do something here. If newer environments cause failures
> > like this, it seems likely that this will spread to more and more
> > applications
> > over time...
> >
>
> Just to reassure myself I have not been hallucinating, I repeated the test.
>
>
> pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf/root/HEAD/inst
> $ /usr/bin/perl -e 'system(qq{"bin/pg_ctl" -D data-C -w -l logfile start >
> startlog 2>&1}) ; print $? ? "BANG: $?\n" : "OK\n";'
> OK
>
> pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf/root/HEAD/inst
> $ /usr/bin/perl -e 'system(qq{"bin/pg_ctl" -D data-C -w -l logfile stop >
> stoplog 2>&1}) ; print $? ? "BANG: $?\n" : "OK\n";'
> BANG: 33280
Oh, so it only happens when stopping, never when starting? That's
interesting...
> If you want to play I can arrange access.
That'd be very helpful.
Greetings,
Andres Freund
