Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncSNZ-0008Nl-08 for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 13:40:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ncSNX-0008UB-Pq for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 13:40:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncSNX-0008P1-GF for pgsql-hackers@lists.postgresql.org; Thu, 07 Apr 2022 13:40:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncSNV-0007JF-6j for pgsql-hackers@lists.postgresql.org; Thu, 07 Apr 2022 13:40:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 237DehfM3278491; Thu, 7 Apr 2022 09:40:43 -0400 From: Tom Lane To: Michael Paquier cc: Thomas Munro , Andres Freund , Julien Rouhaud , Niyas Sait , PostgreSQL Hackers Subject: Re: [PATCH] Add native windows on arm64 support In-reply-to: References: <20220322103011.i6z2tuj4hle23wgx@jrouhaud> <20220324011531.va6z5pst5ygtu6zu@alap3.anarazel.de> Comments: In-reply-to Michael Paquier message dated "Thu, 07 Apr 2022 15:36:19 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3278489.1649338843.1@sss.pgh.pa.us> Date: Thu, 07 Apr 2022 09:40:43 -0400 Message-ID: <3278490.1649338843@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Fri, Mar 25, 2022 at 11:38:44AM +1300, Thomas Munro wrote: >> Yeah. I think we should commit this patch, but decree that >> Windows/aarch64 support is experimental only for now. That allows a >> build farm animal to be set up. Then we add a bit of extra logging >> and see how it does running our test suite over time and learn more. > I don't have such a setup so my testing capabilities are limited. > Does anybody have one? I think that we could be flexible for this > patch, even after feature freeze as it introduces something entirely > new without impacting the existing code. The patch has been moved to > the next CF for now. I dunno, the lack of any in-house capability for this makes me very nervous. If it causes problems down the road, how will we debug it? So it seems like the sort of patch to put in at the beginning of a development cycle, not post-feature-freeze. regards, tom lane