Hi,
I was writing emails in the browser. I am writing this letter and
sending it in the mail client. The letter format is plain text. I think
this should fix the problem.
You do not need to check for files in the pg_commit_ts directory in the
new cluster BEFORE the copy operation. These files are not needed. This
patch is designed to copy the pg_commit_ts directory from the old
cluster. If the user does not want to copy the pg_commit_ts directory,
it is enough not to specify the --pg-commit-ts option. This is the
default behavior. And for most, this is a suitable option.
27.07.2026 10:54, Hayato Kuroda (Fujitsu) пишет:
Dear Sergey,
(BTW, your mail looks broken on the web mail archive [1]. Please check settings)
Are you talking about checking for files in the pg_commit_ts directory of the
old cluster?
The possibility of copying the catalog is checked here:
No. IIUC, the code check whether the old node has a commit timestamps, and
copies them
if it has.
My scenario was that if the NEW node has already had a commit timestamps. In
this case,
existing entries would be overwritten after the upgrade. Then my question was
that whether
we need to ensure there are no commit timestamp entries in the new cluster.
[1]: https://www.postgresql.org/message-id/[email protected]
Best regards,
Hayato Kuroda
FUJITSU LIMITED
