Hi,

Yes, track_commit_timestamp must be installed in the new instance.

This is only the responsibility of an experienced user.

pg_upgrage should allow you to save pg_commit_ts if this data exists at the time of migration.

Warnings are not needed, the loss of this data is not critical in most cases. They were lost with each migration if users did not manually migrate them.

----------------

Кому: 'ls7777' (ls7777@yandex.ru);

Копия: pgsql-hackers@postgresql.org;

Тема: Patch for migration of the pg_commit_ts directory;

01.10.2025, 17:17, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>:

Hi,

Per my understanding, track_commit_timestamp must be on the new instance,
otherwise it would be removed when new instance starts. Is it correct?
If so, should we detect the difference and do some warnings/errors here?
Or it is just the user's responsibility?

Best regards,
Hayato Kuroda
FUJITSU LIMITED