Re: Cygwin cleanup - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Cygwin cleanup
Date
Msg-id CA+TgmoYn1wNOpx7FJU6aHn_=d6JOMkGgcijpH6cMVnyBfJGYBg@mail.gmail.com
Whole thread Raw
In response to Re: Cygwin cleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Cygwin cleanup
List pgsql-hackers
On Tue, Jul 26, 2022 at 7:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think maybe we should re-open the discussion.  I've certainly
> reached the stage of fed-up-ness.  That platform seems seriously
> broken, upstream is making no progress on fixing it, and there
> doesn't seem to be any real-world use-case.  The only positive
> argument for it is that Readline doesn't work in the other
> Windows builds --- but we've apparently not rechecked that
> statement in eighteen years, so maybe things are better now.
>
> If we could just continue to blithely ignore lorikeet's failures,
> I wouldn't mind so much; but doing any significant amount of new
> code development work for the platform seems like throwing away
> developer time.

I agree with that. All things being equal, I like the idea of
supporting a bunch of different platforms, and Cygwin doesn't really
look that dead. It has recent releases. But if blocking signals
doesn't actually work on that platform, making PostgreSQL work
reliably there seems really difficult.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: making relfilenodes 56 bits
Next
From: Justin Pryzby
Date:
Subject: Re: Password reset link / 'less' does not exit in psql version 13.4