Re: Patch for migration of the pg_commit_ts directory

ls7777 <ls7777@yandex.ru>

From: ls7777 <ls7777@yandex.ru>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "orlovmg@gmail.com" <orlovmg@gmail.com>
Date: 2026-03-10T14:39:59Z
Lists: pgsql-hackers

Attachments

<div>Hello,</div><div> </div><div><div>I don't understand what I need to do.</div></div><div> </div><div><blockquote><div>Subject: [PATCH v10] Migration of the pg_commit_ts directory</div></blockquote></div><div> </div><div><div>I have specified a new version in the patch. Do I need to add anything else?</div></div><div> </div><div>----------------</div><div>Кому: 'ls7777' (ls7777@yandex.ru);</div><div>Копия: pgsql-hackers@postgresql.org, orlovmg@gmail.com;</div><div>Тема: Patch for migration of the pg_commit_ts directory;</div><div>10.03.2026, 07:50, "Hayato Kuroda (Fujitsu)" &lt;kuroda.hayato@fujitsu.com&gt;:</div><blockquote><p>Dear Sergey,<br /><br />You seemed to merge the patch correctly, but missing update the commit message.<br /><br />Best regards,<br />Hayato Kuroda<br />FUJITSU LIMITED<br /> </p></blockquote>



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Update copyright for 2026