Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWYBO-0001ww-0S for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jan 2018 01:49:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWYBN-00017j-Dn for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jan 2018 01:49:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eWYBN-00017a-7V for pgsql-hackers@lists.postgresql.org; Wed, 03 Jan 2018 01:49:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eWYBG-0008PE-DB for pgsql-hackers@lists.postgresql.org; Wed, 03 Jan 2018 01:49:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w031nIMg018677; Tue, 2 Jan 2018 20:49:18 -0500 From: Tom Lane To: Andres Freund cc: Thomas Munro , pgsql-hackers@lists.postgresql.org Subject: Re: Ensuring hash tuples are properly maxaligned In-reply-to: <20180103014355.52an4fgwigdzhzxh@alap3.anarazel.de> References: <14483.1514938129@sss.pgh.pa.us> <20180103010931.6vsirlb5pdapdroq@alap3.anarazel.de> <17454.1514942419@sss.pgh.pa.us> <20180103013300.cf4jermw5ksygm7l@alap3.anarazel.de> <18301.1514943650@sss.pgh.pa.us> <20180103014355.52an4fgwigdzhzxh@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 02 Jan 2018 17:43:55 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18675.1514944157.1@sss.pgh.pa.us> Date: Tue, 02 Jan 2018 20:49:17 -0500 Message-ID: <18676.1514944157@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2018-01-02 20:40:50 -0500, Tom Lane wrote: >> OK, then there's not a live bug, but I'm a bit tempted to get rid of >> the data[] member anyway. It's not clear to me now that keeping it >> results in net cleaner code. Thoughts? > I like that plan. I don't think the data field buys us anything, and I > personally in most cases find "fully manual" alignment code easier to > reason about than fiddling with padding fields. Agreed --- I'll go do that. regards, tom lane