Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Subject: Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~
Date: 2022-05-26 20:59:01
Message-ID: CA+hUKGL+Qcq=qAzKcUUaNGJhOhBRE1XHz05YPZMwO8qY8YztdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 26, 2022 at 4:27 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Perhaps the async work?

(Checks code...) Looks like the experimental Windows native AIO code
we have today, namely io_method=windows_iocp, only needs Vista.
That's for GetQueueCompletionStatusEx() (before that you had to call
GetQueuedCompletionStatus() in a loop to read multiple IO completion
events from an IOCP), and otherwise it's all just ancient Windows
"overlapped" stuff. Not sure if we'll propose that io_method, or skip
directly to the new io_uring-style API that appeared in Win 11 (not
yet tried), or propose both as long as Win 10 is around, or ... I
dunno.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-05-26 21:08:07 Status of cluster file encryption
Previous Message Michael Paquier 2022-05-26 20:57:39 Re: Remove support for Visual Studio 2013