| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'ls7777' <ls7777(at)yandex(dot)ru>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "orlovmg(at)gmail(dot)com" <orlovmg(at)gmail(dot)com>, "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | RE: Patch for migration of the pg_commit_ts directory |
| Date: | 2026-05-12 00:42:28 |
| Message-ID: | OS9PR01MB12149E5D3EB7ECC31EC27683BF5392@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Sergey,
I found that Ajin started another thread which migrates replication origins [1].
So how about purging the part from this patch? I.e., commit_ts migrations would
be migrated well if both patches are pushed. To keep the behavior consistent,
[1] may have to be pushed first.
Personally considered, added checks in the patch may look bit ad-hoc, and we
should fix from the root cause.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2026-05-12 00:57:09 | Re: [SQL/PGQ] Early pruning for GRAPH_TABLE path generation |
| Previous Message | Sami Imseih | 2026-05-12 00:35:55 | Re: Improve pg_stat_statements scalability |