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 1oclq6-0000zO-35 for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Sep 2022 10:59:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oclq4-0002DK-UW for pgsql-bugs@arkaria.postgresql.org; Mon, 26 Sep 2022 10:59:52 +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 1oclq4-0002Cb-Lh for pgsql-bugs@lists.postgresql.org; Mon, 26 Sep 2022 10:59:52 +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 1oclq2-0007TN-DD for pgsql-bugs@lists.postgresql.org; Mon, 26 Sep 2022 10:59:51 +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 28QAxl3Z3334939; Mon, 26 Sep 2022 06:59:47 -0400 From: Tom Lane To: Michael Paquier cc: Masahiko Sawada , Justin Pryzby , Dmitry Koval , Dilip Kumar , andrewbille@gmail.com, pgsql-bugs@lists.postgresql.org, Kyotaro Horiguchi Subject: Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end In-reply-to: References: <20220628003720.GG19662@telsasoft.com> <2604497.1664053071@sss.pgh.pa.us> <3269450.1664165784@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Mon, 26 Sep 2022 18:54:59 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3334937.1664189987.1@sss.pgh.pa.us> Date: Mon, 26 Sep 2022 06:59:47 -0400 Message-ID: <3334938.1664189987@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Mon, Sep 26, 2022 at 12:16:24AM -0400, Tom Lane wrote: >> Yeah, but why? I see no good reason why those fields need to be first. > My reasoning on these ones is that we are most likely going to add > more description flags in the future than new unit types. Perhaps I > am wrong. Sure, but we could easily leave unused bits there. Aligning the units subfields on byte boundaries might result in slightly better machine code, anyway. regards, tom lane