Re: Patch for migration of the pg_commit_ts directory

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: ls7777 <ls7777@yandex.ru>

Cc: Maxim Orlov <orlovmg@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2025-10-06T15:45:15Z

Lists: pgsql-hackers

On Mon, Oct  6, 2025 at 07:31:52PM +0500, ls7777 wrote:
> Hi,
> I'll try to return it to the original thread.
>  
> I absolutely agree with you. Data loss during migration is an unacceptable
> situation. And why it's still happening, I don't understand. But issuing
> messages will require translating it into other languages and complicate the
> patch.  I'm not a programmer to do it beautifully. And not a beautiful patch is
> unlikely to be accepted. 
> I will do a parameter check and an ERROR message.

You don't need to worry about translations.  Each language team will
make sure your English message is translated.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

Commits

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