Re: A assert failure when initdb with track_commit_timestamp=on

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Andy Fan <zhihuifan1213(at)163(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A assert failure when initdb with track_commit_timestamp=on
Date: 2025-07-03 00:48:40
Message-ID: 1f8f703d-72e8-4d05-ab16-ff0403a1d19d@oss.nttdata.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-07-03 01:13:19 Re: A assert failure when initdb with track_commit_timestamp=on
Previous Message Richard Guo 2025-07-03 00:30:07 Re: Reduce "Var IS [NOT] NULL" quals during constant folding