Re: A assert failure when initdb with track_commit_timestamp=on

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: 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 01:13:19
Message-ID: aGXZL0oraweaENrF@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 03, 2025 at 09:48:40AM +0900, Fujii Masao wrote:
> Is this the same issue that was discussed in [1]?
>
> [1] https://postgr.es/m/OSCPR01MB14966FF9E4C4145F37B937E52F5102@OSCPR01MB14966.jpnprd01.prod.outlook.com

Ah, indeed, so it was reported a couple of months ago. I am not sure
that the argument about all the other GUCs potentially impacted holds
much value; we are talking about a specific code path.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-07-03 01:16:57 Re: Inconsistent LSN format in pg_waldump output
Previous Message Fujii Masao 2025-07-03 00:48:40 Re: A assert failure when initdb with track_commit_timestamp=on