Re: Windows now has fdatasync() - Mailing list pgsql-hackers

From Dave Page
Subject Re: Windows now has fdatasync()
Date
Msg-id CA+OCxox2A_nxjMvi=48SaG9YbM8SJzQTFTzPV5Nr3+P0nok8cw@mail.gmail.com
Whole thread Raw
In response to Re: Windows now has fdatasync()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Windows now has fdatasync()  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers


On Fri, 8 Apr 2022 at 05:41, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Apr 08, 2022 at 02:56:15PM +1200, Thomas Munro wrote:
>> I propose that we drop support for Windows versions older than
>> 10/Server 2016 in the PostgreSQL 16 cycle,

Do we have any data on what people are actually using?

None that I know of. Anecdotally, we dropped support for pgAdmin on Windows < 8 (2012 for the server edition), and had a single complaint - and the user happily acknowledged they were on an old release and expected support to be dropped sooner or later. Windows 8 was a pretty unpopular release, so I would expect shifting to 10/2016+ for PG 16 would be unlikely to be a major problem.

FWIW, Python dropped support for < 8/2012 with v3.9.
 

> Do you think that we could raise the minimum C standard on WIN32 to
> C11, at least for MSVC?

As long as the C11-isms are in MSVC-only code, it seems like this is
exactly equivalent to setting a minimum MSVC version.  I don't see
an objection-in-principle there, it's just a practical question of
how far back is reasonable to support MSVC versions.  (That's very
distinct from how far back we need the built code to run.)

                        regards, tom lane




--

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: BufferAlloc: don't take two simultaneous locks
Next
From: Markus Wanner
Date:
Subject: Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.]