From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
        Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Cygwin cleanup
In-reply-to: 
 <CA+hUKGJq=x=yQ77J=btr6ih6jveC35225Gkcm1MrSd5Q3mEdtw@mail.gmail.com>
References: 
 <CA+hUKG+e13wK0PBX5Z63CCwWm7MfRQuwBRabM_3aKWSko2AUww@mail.gmail.com>
 <2143450.1658810058@sss.pgh.pa.us>
 <CA+hUKGJq=x=yQ77J=btr6ih6jveC35225Gkcm1MrSd5Q3mEdtw@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Tue, 26 Jul 2022 17:16:48 +1200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2228594.1658835647.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jul 2022 07:40:47 -0400
Message-ID: <2228595.1658835647@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2228595.1658835647%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> On Tue, Jul 26, 2022 at 4:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> If that's an accurate statement, shouldn't we just drop Cygwin support?

> This thread rejected the idea last time around:
> https://www.postgresql.org/message-id/flat/136712b0-0619-5619-4634-0f028=
6acaef7%402ndQuadrant.com

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.

			regards, tom lane