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 1o7kil-0000wu-0a for pgsql-hackers@arkaria.postgresql.org; Sat, 02 Jul 2022 21:32:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o7kij-0006jJ-1m for pgsql-hackers@arkaria.postgresql.org; Sat, 02 Jul 2022 21:32:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7kii-0006jA-P0 for pgsql-hackers@lists.postgresql.org; Sat, 02 Jul 2022 21:32:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7kif-0005kq-6V for pgsql-hackers@postgresql.org; Sat, 02 Jul 2022 21:32:03 +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 262LVsel985076; Sat, 2 Jul 2022 17:31:54 -0400 From: Tom Lane To: Andres Freund cc: Peter Geoghegan , Noah Misch , PostgreSQL Hackers Subject: Re: AIX support - alignment issues In-reply-to: <20220702205149.k5qp42n2ztuuhui2@alap3.anarazel.de> References: <20220702183354.a6uhja35wta7agew@alap3.anarazel.de> <968410.1656789743@sss.pgh.pa.us> <977853.1656794075@sss.pgh.pa.us> <20220702205149.k5qp42n2ztuuhui2@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Sat, 02 Jul 2022 13:51:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <985074.1656797514.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 02 Jul 2022 17:31:54 -0400 Message-ID: <985075.1656797514@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > What made me look at this issue right now is that the alignment issue le= ad the > 56bit relfilenode patch to move the relfilenode field to the start of pg= _class > (ahead of the oid), Agreed, up with that we should not put. However ... > because a 64bit value cannot be after a NameData. ... this coding rule strikes me as utterly ridiculous. Why can't we instead insist that NAMEDATALEN must be a multiple of 8? Anyone who tries to make it different from that is likely to be wasting padding space even on platforms where there's not a deeper problem. regards, tom lane