Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rq2at-00AEFL-LI for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2024 03:07:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rq2as-009OT1-QJ for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2024 03:07:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rq2as-009OSt-HF for pgsql-hackers@lists.postgresql.org; Fri, 29 Mar 2024 03:07:50 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rq2ao-006z57-1l for pgsql-hackers@postgresql.org; Fri, 29 Mar 2024 03:07:49 +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 42T37gub3833448; Thu, 28 Mar 2024 23:07:42 -0400 From: Tom Lane To: Noah Misch cc: Sriram RK , Alvaro Herrera , "pgsql-hackers@postgresql.org" Subject: Re: AIX support In-reply-to: <20240329024832.a0@rfd.leadboat.com> References: <322245.1711029459@sss.pgh.pa.us> <20240329024832.a0@rfd.leadboat.com> Comments: In-reply-to Noah Misch message dated "Thu, 28 Mar 2024 19:48:32 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3833446.1711681662.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Mar 2024 23:07:42 -0400 Message-ID: <3833447.1711681662@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Noah Misch writes: > On Thu, Mar 28, 2024 at 11:09:43AM +0000, Sriram RK wrote: >> Also, would like to know if we can access the buildfarm(power machines)= to run any of the specific tests to hit this assert. > https://portal.cfarm.net/users/new/ is the form to request access. It l= ists > the eligibility criteria. There might be some confusion here about what system we are talking about. The Postgres buildfarm is described at https://buildfarm.postgresql.org/index.html but it consists of a large number of individual machines run by individual owners. There would not be a lot of point in adding a new AIX machine to the Postgres buildfarm right now, because it would surely fail to build HEAD. What Noah is referencing is the GCC compile farm, which happens to include some AIX machines. The existing AIX entries in the Postgres buildfarm are run (by Noah) on those GCC compile farm machines, which really the GCC crowd have been *very* forgiving about letting us abuse like that. If you have your own AIX hardware there's not a lot of reason that you should need to access the GCC farm. What you do need to do to reproduce the described problems is check out the Postgres git tree and rewind to just before commit 0b16bb877, where we deleted AIX support. Any attempt to restore AIX support would have to start with reverting that commit (and perhaps the followup f0827b443). regards, tom lane