RE: Patch for migration of the pg_commit_ts directory

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Maxim Orlov' <orlovmg(at)gmail(dot)com>
Cc: Sergey <ls7777(at)yandex(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "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-11-13 09:03:28
Message-ID: OS7PR01MB18317647423861F6A5C4E3A17F57F2@OS7PR01MB18317.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Maxim,

Thanks for the reply and sorry for the late response.

> With 0001, we are effectively modifying the permissible XID range for
> tuples. XIDs limits are restored from old cluster. Then lookup will
> succeed and conflict detection will be reported. This is likely false
> positive, but very annoying.

Sorry, I'm still bit unclear the situation. Can you share me a concrete reproducer
to demonstrate it?

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-11-13 09:04:21 RE: Patch for migration of the pg_commit_ts directory
Previous Message Andreas Karlsson 2026-11-13 08:52:49 Re: Add sortsupport to money_ops, pg_lsn_ops and xid8_ops