RE: Patch for migration of the pg_commit_ts directory

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Maxim Orlov' <orlovmg(at)gmail(dot)com>, ls7777 <ls7777(at)yandex(dot)ru>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Patch for migration of the pg_commit_ts directory
Date: 2025-10-01 12:27:25
Message-ID: OSCPR01MB149662EADD1EDA9811E7DF2B6F5E6A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Maxim,

Thanks for considering the test case. To confirm, where should we put the test code?
Pp_upgrade has already had 006 test, and commit_ts has not had 005 test.

Regarding the test, it is enough to check whether oldest/newest transactions on the old
cluster can be tracked.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2025-10-01 12:27:52 Re: split func.sgml to separated individual sgml files
Previous Message Hayato Kuroda (Fujitsu) 2025-10-01 12:17:50 RE: Patch for migration of the pg_commit_ts directory