pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Andy Fan <zhihuifan1213@163.com>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: A assert failure when initdb with track_commit_timestamp=on
Date: Thu, 3 Jul 2025 09:48:40 +0900
Message-ID: <1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com> (raw)
In-Reply-To: <87plejmnpy.fsf@163.com>
References: <87plejmnpy.fsf@163.com>



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






view thread (28+ messages)  latest in thread

Message-ID: <1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com>
Permalink:  ../1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com/
Also on:    postgresql.org/message-id/1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, zhihuifan1213@163.com
  Subject: Re: A assert failure when initdb with track_commit_timestamp=on
  In-Reply-To: <1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox