Re: Patch for migration of the pg_commit_ts directory

<div><div>Hi,</div><div> </div><div>We use the transaction commit time to answer questions about when a record in any table was changed.</div><div>The main use is to detect application errors. It is used only by DB administrators. Transaction information is stored for up to 2 years.</div><div>The "temporary" nature of this information prevents the transaction commit time from being used more widely.</div></div><div> </div><div><div>We copied the pg_commit_ts directory manually. But it's unreliable.</div><div>Can I add a command line option?</div><div>So that the decision to migrate pg_commit_ts is made by the user ?</div></div><div> </div><div>----------------</div><div>Кому: 'ls7777' (ls7777@yandex.ru), Masahiko Sawada (sawada.mshk@gmail.com);</div><div>Копия: pgsql-hackers@postgresql.org, orlovmg@gmail.com, amit.kapila16@gmail.com;</div><div>Тема: Patch for migration of the pg_commit_ts directory;</div><div>19.03.2026, 10:31, "Hayato Kuroda (Fujitsu)" &lt;kuroda.hayato@fujitsu.com&gt;:</div><blockquote><p>Dear Sergey,<br /> </p><blockquote> This is a safer strategy to help you avoid losing the data that the user needs. I received a recommendation to do so.</blockquote><p><br />I think we need stronger use-case to proceed like that.<br />Did you get recommendations from customers/users? If so, why do they want to<br />avoid losing the commit timestamp? Are they collaborating some other systems?<br />Your voice/experience is really needed.<br /><br />Best regards,<br />Hayato Kuroda<br />FUJITSU LIMITED<br /> </p></blockquote>