MIME-Version: 1.0
References: <916d0fd1-a99b-41c4-a017-ff2428bf8cca@dunslane.net>
In-Reply-To: <916d0fd1-a99b-41c4-a017-ff2428bf8cca@dunslane.net>
From: Aleksander Alekseev <aleksander@timescale.com>
Date: Tue, 22 Apr 2025 15:10:51 +0300
Message-ID: 
 <CAJ7c6TNyAs_s7+5C4uZBvwoxsnYPDonR0r2zSJ5EpdH0-oz7TA@mail.gmail.com>
Subject: Re: Cygwin support
To: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJ7c6TNyAs_s7%2B5C4uZBvwoxsnYPDonR0r2zSJ5EpdH0-oz7TA%40mail.gmail.com>
Precedence: bulk

Hi Andrew,

> Last year the old Windows machine where I was running the buildfarm
> member lorikeet died, and since then we've had no buildfarm coverage for
> Cygwin. I now have a new (but slow) W11pro machine and I have been
> testing out Cygwin builds on it. I wanted to have it running the TAP
> tests, unlike lorikeet. Attached is a set of very small patches aimed at
> enabling this.
>
> [...]

Thanks for the patches.

I wonder though if it is advisable to support Cygwin if this requires
extra effort from our side, compared to a regular Linux or Windows
environment. I actually like the project but I wouldn't recommend
running Postgres on prod, and for development these days it's simpler
to use WSL / VirtualBox / Raspberry Pi, or running Postgres natively
on Windows.

-- 
Best regards,
Aleksander Alekseev