RE: A assert failure when initdb with track_commit_timestamp=on

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Michael Paquier' <michael(at)paquier(dot)xyz>, 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:30:29
Message-ID: OSCPR01MB14966207D000875CA4F4C9FEAF543A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Michael, Fujii-san,

> 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.

Yeah, I did report but sadly it was missed by others :-(. To clarify,
The current patch looks good to me.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-07-03 01:30:40 Re: Add progressive backoff to XactLockTableWait functions
Previous Message Merlin Moncure 2025-07-03 01:19:08 Re: libpq: Process buffered SSL read bytes to support records >8kB on async API