Hi,

We use the transaction commit time to answer questions about when a record in any table was changed.

The main use is to detect application errors. It is used only by DB administrators. Transaction information is stored for up to 2 years.

The "temporary" nature of this information prevents the transaction commit time from being used more widely.

We copied the pg_commit_ts directory manually. But it's unreliable.

Can I add a command line option?

So that the decision to migrate pg_commit_ts is made by the user ?

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

Кому: 'ls7777' (ls7777@yandex.ru), Masahiko Sawada (sawada.mshk@gmail.com);

Копия: pgsql-hackers@postgresql.org, orlovmg@gmail.com, amit.kapila16@gmail.com;

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

19.03.2026, 10:31, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>:

Dear Sergey,

This is a safer strategy to help you avoid losing the data that the user needs. I received a recommendation to do so.

I think we need stronger use-case to proceed like that.
Did you get recommendations from customers/users? If so, why do they want to
avoid losing the commit timestamp? Are they collaborating some other systems?
Your voice/experience is really needed.

Best regards,
Hayato Kuroda
FUJITSU LIMITED