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 1rf4L1-00FFzK-KU for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Feb 2024 20:46:08 +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 1rf4L0-0065eH-1X for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Feb 2024 20:46:06 +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 1rf4Kz-0065e8-Oo for pgsql-hackers@lists.postgresql.org; Tue, 27 Feb 2024 20:46:06 +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 1rf4Ku-001bFe-Sa for pgsql-hackers@postgresql.org; Tue, 27 Feb 2024 20:46:04 +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 41RKjjVd2153381; Tue, 27 Feb 2024 15:45:45 -0500 From: Tom Lane To: Heikki Linnakangas cc: Michael Paquier , Robert Haas , Noah Misch , Thomas Munro , Andres Freund , Peter Smith , vignesh C , pgsql-hackers , Melanie Plageman Subject: Re: Relation bulk write facility In-reply-to: <3a0d22fa-7613-4881-aa19-ddd31fb92cc0@iki.fi> References: <20240224195024.af@rfd.leadboat.com> <20240224212936.f3zcbs24f7oaapm4@alap3.anarazel.de> <0C469A7A-548C-4B0C-9495-730FE80046E1@iki.fi> <31db8d41-2ac9-4b5e-b7a8-712d6d7d7aa2@iki.fi> <20240225194322.a5@rfd.leadboat.com> <1535845.1708890691@sss.pgh.pa.us> <3a0d22fa-7613-4881-aa19-ddd31fb92cc0@iki.fi> Comments: In-reply-to Heikki Linnakangas message dated "Wed, 28 Feb 2024 00:24:01 +0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2153378.1709066745.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Feb 2024 15:45:45 -0500 Message-ID: <2153379.1709066745@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Heikki Linnakangas writes: > What do y'all think of adding a check for = > ALIGNOF_DOUBLE=3D=3DMAXIMUM_ALIGNOF to configure.ac and meson.build? It'= s = > not a requirement today, but I believe AIX was the only platform where = > that was not true. With AIX gone, that combination won't be tested, and = > we will probably break it sooner or later. +1, and then probably revert the whole test addition of 79b716cfb7a. I did a quick scrape of the buildfarm, and identified these as the only animals reporting ALIGNOF_DOUBLE less than 8: $ grep 'alignment of double' alignments | grep -v ' 8$' hornet | 2024-02-22 16:26:16 | checking alignment of double... 4 lapwing | 2024-02-27 12:40:15 | checking alignment of double... (ca= ched) 4 mandrill | 2024-02-19 01:03:47 | checking alignment of double... 4 sungazer | 2024-02-21 00:22:48 | checking alignment of double... 4 tern | 2024-02-22 13:25:12 | checking alignment of double... 4 With AIX out of the picture, lapwing will be the only remaining animal testing MAXALIGN less than 8. That seems like a single point of failure ... should we spin up another couple 32-bit animals? I had supposed that my faithful old PPC animal mamba was helping to check this, but I see that under NetBSD it's joined the ALIGNOF_DOUBLE=3D=3D8 crowd. regards, tom lane