RE: Patch for migration of the pg_commit_ts directory

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>

To: 'ls7777' <ls7777@yandex.ru>, Masahiko Sawada <sawada.mshk@gmail.com>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "orlovmg@gmail.com" <orlovmg@gmail.com>, "amit.kapila16@gmail.com" <amit.kapila16@gmail.com>

Date: 2026-03-19T05:30:41Z

Lists: pgsql-hackers

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

Commits

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