Re: A assert failure when initdb with track_commit_timestamp=on

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>

To: Andy Fan <zhihuifan1213@163.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-07-03T00:48:40Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Disable commit timestamps during bootstrap
- 8bca4476f9f9 13.22 landed
- b61ddcaf41cf 14.19 landed
- dcbbd43317c0 15.14 landed
- 7e7059abfd22 16.10 landed
- ae20c105f0b2 17.6 landed
- 29a4b63c6bc8 18.0 landed
- 5a6c39b6df33 19 (unreleased) landed


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