| 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-03-27 02:12:23 |
| Message-ID: | OS9PR01MB12149BE9CB3DAD29D6B7FB68BF557A@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Sergey,
Sorry for being late, I was busy in another project.
Not sure we have enough time to rush this for PG19 because some new parts are
added recently.
Personally considered, the patch might be able to separate into two parts.
0001 contains changes to migrate the replication origin, and 0002 contains to
migrate the commit_ts directory. For 0001, we may need a new SQL function to
migrate replication origins, and it could be used only while in the binary upgrade
mode like binary_upgrade_add_sub_rel_state(). We must not directly update the
system catalog via UPDATE command. 0002 might be the same as what we discussed
earlier.
> 1. Added the --pg-commit-ts command line key for pg_upgrade.
> Migration of the pg_commit_ts directory will be performed only if the user explicitly wishes.
I cannot find the reason why you changed here. Can you share me your opinion?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-03-27 02:59:33 | Re: [Proposal] pg_stat_wal_records – per-record-type WAL generation statistics |
| Previous Message | Lukas Fittl | 2026-03-27 01:50:20 | Re: Refactor query normalization into core query jumbling |