Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: [PATCH] Add native windows on arm64 support
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <3278490.1649338843@sss.pgh.pa.us>
Date: Thu, 7 Apr 2022 16:55:27 +0200
Cc: Michael Paquier <michael@paquier.xyz>,
 Thomas Munro <thomas.munro@gmail.com>,
 Andres Freund <andres@anarazel.de>,
 Julien Rouhaud <rjuju123@gmail.com>,
 Niyas Sait <niyas.sait@linaro.org>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: 7bit
Message-Id: <DBD80715-E56B-40EB-84AA-ACE70198E7AD@yesql.se>
References: <CAFPTBD-74+AEuN9n7caJ0YUnW5A0r-KBX8rYoEJWqFPgLKpzdg@mail.gmail.com>
 <CA+hUKG+bPsp45=86xoDeX2do4zOUaaD1nAhVmPhaO8k5OYs2LA@mail.gmail.com>
 <CAFPTBD_NZb=q_6uE-QV+S+pm=Rc9sBKrg8CQ_Y3dc27Awrm7cQ@mail.gmail.com>
 <20220322103011.i6z2tuj4hle23wgx@jrouhaud>
 <CA+hUKGJDYZ3NRTQ8DtTrO6oshaYy2wPszj1jKAUm_zD1zbCm-Q@mail.gmail.com>
 <20220324011531.va6z5pst5ygtu6zu@alap3.anarazel.de>
 <CA+hUKGKGZ2crHGDi=zXtjYy9GptUZ99Jtu=w-P_qeaeaP8k7mg@mail.gmail.com>
 <Yk6GY8A8MNTQE6iz@paquier.xyz> <3278490.1649338843@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/DBD80715-E56B-40EB-84AA-ACE70198E7AD%40yesql.se>
Precedence: bulk

> On 7 Apr 2022, at 15:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Michael Paquier <michael@paquier.xyz> 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?

If those with an interest in such platform support cannot spare the cycles to
at least run a buildfarm member, then it seems a stretch for us to maintain
such support with any confidence.

> So it seems like the sort of patch to put in at the beginning of a
> development cycle, not post-feature-freeze.

+1

--
Daniel Gustafsson		https://vmware.com/