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 1poTYc-0001m6-Bj for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Apr 2023 18:26:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1poTYb-0004Kd-6F for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Apr 2023 18:26:29 +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 1poTYa-0004K6-T8 for pgsql-hackers@lists.postgresql.org; Mon, 17 Apr 2023 18:26:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1poTYY-003Tb6-NH for pgsql-hackers@postgresql.org; Mon, 17 Apr 2023 18:26:28 +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 33HIQMg72496924; Mon, 17 Apr 2023 14:26:22 -0400 From: Tom Lane To: Andres Freund cc: Matthias van de Meent , Justin Pryzby , pgsql-hackers@postgresql.org Subject: Re: v16dev: TRAP: failed Assert("size > SizeOfXLogRecord"), File: "xlog.c", Line: 1055, PID: 13564 In-reply-to: <20230417180009.akas7axm6vn5lxma@awork3.anarazel.de> References: <2444561.1681748021@sss.pgh.pa.us> <2454846.1681753830@sss.pgh.pa.us> <20230417180009.akas7axm6vn5lxma@awork3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 17 Apr 2023 11:00:09 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2496922.1681755982.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Apr 2023 14:26:22 -0400 Message-ID: <2496923.1681755982@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > On 2023-04-17 13:50:30 -0400, Tom Lane wrote: >> So previously, log_newpage_range could only have failed in very >> unlikely circumstances, whereas now it's not hard to hit when >> committing a table creation. I wonder what other bugs may be >> lurking. > Oh, interesting. We haven't initialized the extra pages added by > RelationAddExtraBlocks() (in <=3D 15) for quite a while now, so I'm a bi= t > surprised it causes more issues for the VM / FSM. I guess it's that it's= quite > common in real workloads to contend on the extension lock and add extra > blocks, but not in simple single-threaded tests? I haven't tried hard to run it to ground, but maybe log_newpage_range isn't used in that code path? Seems like we'd have detected this before now if the case were reachable without any crash involved. regards, tom lane