| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: intermittent failures in Cygwin from select_parallel tests |
| Date: | 2021-06-23 03:02:28 |
| Message-ID: | 20210623030228.GA1421448@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 22, 2021 at 08:18:42AM -0400, Andrew Dunstan wrote:
> On 6/22/21 2:42 AM, Noah Misch wrote:
> > I was wondering about suggesting some kind of
> >> official warning, but I guess the manual already covers it with this
> >> 10 year old notice. I don't know much about Windows or Cygwin so I'm
> >> not sure if it needs updating or not, but I would guess that there are
> >> no longer any such systems?
> >>
> >> <productname>Cygwin</productname> is not recommended for running a
> >> production server, and it should only be used for running on
> >> older versions of <productname>Windows</productname> where
> >> the native build does not work.
> > I expect native builds work on all Microsoft-supported Windows versions, so +1
> > for removing everything after the comma.
>
> If we just want to declare Cygwin unsupported I can halt lorikeet and we
> can be done with it.
No way. lorikeet is valuable.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2021-06-23 03:39:58 | Re: [HACKERS] logical decoding of two-phase transactions |
| Previous Message | Amit Kapila | 2021-06-23 02:53:31 | Re: Optionally automatically disable logical replication subscriptions on error |