From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Cygwin support |
Date: | 2025-04-22 12:10:51 |
Message-ID: | CAJ7c6TNyAs_s7+5C4uZBvwoxsnYPDonR0r2zSJ5EpdH0-oz7TA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2025-04-22 12:10:58 | Re: Adding pg_dump flag for parallel export to pipes |
Previous Message | Nisha Moond | 2025-04-22 11:47:17 | Re: Large expressions in indexes can't be stored (non-TOASTable) |