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 1k9Vhu-0002Gq-88 for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Aug 2020 15:45:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k9Vht-0007Yj-4J for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Aug 2020 15:45:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9Vhs-0007Yc-L9 for pgsql-hackers@lists.postgresql.org; Sat, 22 Aug 2020 15:45:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9Vhq-00027T-MP for pgsql-hackers@lists.postgresql.org; Sat, 22 Aug 2020 15:45:23 +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 07MFjICw2155716; Sat, 22 Aug 2020 11:45:18 -0400 From: Tom Lane To: Bruce Momjian cc: "David G. Johnston" , Antonin Houska , Andres Freund , PostgreSQL Hackers Subject: Re: xl_heap_header alignment? In-reply-to: <20200822153734.GA26781@momjian.us> References: <21643.1595353537@antos> <5A0F3128-D990-4431-9E97-793CD99FF11E@anarazel.de> <1058724.1595356403@sss.pgh.pa.us> <22193.1595393913@antos> <20200822004048.GO13363@momjian.us> <20200822153734.GA26781@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Sat, 22 Aug 2020 11:37:34 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2155714.1598111118.1@sss.pgh.pa.us> Date: Sat, 22 Aug 2020 11:45:18 -0400 Message-ID: <2155715.1598111118@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bruce Momjian writes: > Updated patch. FWIW, I concur with the idea of just dropping that sentence altogether. It's not likely that getting rid of that field is a line of development that will ever be pursued; if anyone does get concerned about cutting WAL size, there's a lot of more-valuable directions to go in. regards, tom lane