| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Windows now has fdatasync() |
| Date: | 2022-04-08 02:56:15 |
| Message-ID: | CA+hUKGLcc+07Z9ZjT0MjcSqX46RaPNg388hdbpodysWH6HX-MQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've bumped this to the next cycle, so I can hopefully skip the
missing version detection stuff that I have no way to test (no CI, no
build farm, and I have zero interest in dumpster diving for Windows 7
or whatever installations).
I propose that we drop support for Windows versions older than
10/Server 2016 in the PostgreSQL 16 cycle, because the OS patches for
everything older come to an end in October next year[1], and we have a
lot of patches relating to modern Windows features that stall on
details about old systems that no one actually has.
[1] https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-04-08 03:04:44 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Michael Paquier | 2022-04-08 02:34:17 | Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN |