Re: intermittent failures in Cygwin from select_parallel tests - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: intermittent failures in Cygwin from select_parallel tests
Date
Msg-id 5e6797e9-bc26-ced7-6c9c-59bca415598b@dunslane.net
Whole thread Raw
In response to Re: intermittent failures in Cygwin from select_parallel tests  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 6/22/21 11:02 PM, Noah Misch wrote:
> 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. 



OK, no problem. Leaving it running is not a big deal.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Doc chapter for Hash Indexes
Next
From: "tanghy.fnst@fujitsu.com"
Date:
Subject: RE: Support tab completion for upper character inputs in psql