Re: Compiler warnings with MinGW
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Magnus Hagander <magnus@hagander.net>,
Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-09-17T10:00:39Z
Lists: pgsql-hackers
On 2019-09-09 14:24, Magnus Hagander wrote: > On Sat, Sep 7, 2019 at 4:58 AM Michael Paquier <michael@paquier.xyz > <mailto:michael@paquier.xyz>> wrote: > > On Sat, Sep 07, 2019 at 12:11:25AM +0200, Peter Eisentraut wrote: > > I'm not sure exactly what the upstream of mingw is these days, but I > > think the original issue that led to 811be893 has long been fixed [0], > > and the other stuff in mingwcompat.c is also no longer relevant > [1]. I > > think mingwcompat.c could be removed altogether. I'm not sure to what > > extent we need to support 5+ year old mingw versions. > > On HEAD I would not be against removing that as this leads to a > cleanup of our code. For MSVC, we only support VS 2013~ on HEAD, so > saying that we don't support MinGW older than what was proposed 5 > years ago sounds sensible. > > +1, definitely. committed -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Remove mingwcompat.c
- a25221f53c79 13.0 landed
-
Fix compilation warning of pg_basebackup with MinGW
- 90317ab7e64b 13.0 landed