Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uX8Bh-006AmJ-9X for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Jul 2025 00:52:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uX8Be-0072IJ-VL for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Jul 2025 00:52:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uX887-006v9r-HP for pgsql-hackers@lists.postgresql.org; Thu, 03 Jul 2025 00:48:48 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1uX885-005FVG-1c for pgsql-hackers@postgresql.org; Thu, 03 Jul 2025 00:48:47 +0000 Received: from [192.168.11.9] (p1696134-ipoe.ipoe.ocn.ne.jp [118.0.93.133]) by oss.nttdata.com (Postfix) with ESMTPSA id 8206D618B2; Thu, 3 Jul 2025 09:48:41 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at oss.nttdata.com Message-ID: <1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com> Date: Thu, 3 Jul 2025 09:48:40 +0900 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: A assert failure when initdb with track_commit_timestamp=on Content-Language: en-US To: Andy Fan , PostgreSQL Hackers References: <87plejmnpy.fsf@163.com> From: Fujii Masao In-Reply-To: <87plejmnpy.fsf@163.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2025/07/02 9:38, Andy Fan wrote: > > Hi, > > When working with the commit_ts module, I find the following issue: > > After configure with --enable-cassert option, then initdb with: > > initdb -D x2 -c track_commit_timestamp=on > > Then we can get the following core dump: Is this the same issue that was discussed in [1]? Regards, [1] https://postgr.es/m/OSCPR01MB14966FF9E4C4145F37B937E52F5102@OSCPR01MB14966.jpnprd01.prod.outlook.com -- Fujii Masao NTT DATA Japan Corporation