RE: Patch for migration of the pg_commit_ts directory - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Patch for migration of the pg_commit_ts directory
Date
Msg-id OS9PR01MB12149BC0A686B802D4C8D4FE3F54FA@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Patch for migration of the pg_commit_ts directory  (Masahiko Sawada <sawada.mshk@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: tablecmds: fix bug where index rebuild loses replica identity on partitions
Next
From: JoongHyuk Shin
Date:
Subject: pg_dump: fix NOT NULL constraint name comparison using makeObjectName