| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Sergey' <ls7777(at)yandex(dot)ru> |
| 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>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | RE: Patch for migration of the pg_commit_ts directory |
| Date: | 2026-10-15 03:54:43 |
| Message-ID: | OS7PR01MB18317BB8A8A780A460AED8A5DF59C2@OS7PR01MB18317.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
I did a self reviewing for 0001 and 0002, and updated the doc a bit.
PSA new patch set.
> If you accept part 1, many users who use logical replication will see
> many messages like “conflict detected on relation” that didn’t exist before.
Sorry, I'm not sure the part, can you please clarify more? When can it happen?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v16-0001-pg_upgrade-transfer-commit-timestamps-to-the-new.patch | application/octet-stream | 11.2 KB |
| v16-0002-Add-pg-commit-ts-option.patch | application/octet-stream | 4.8 KB |
| v16-0003-Save-and-restore-roident-and-remote_lsn-for-new-.patch | application/octet-stream | 10.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-10-15 04:17:28 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | shihao zhong | 2026-10-15 03:53:48 | [PG19] Promotion hangs behind a backend blocked on a stuck client |