Assert the timestamp is available for ORIGN_DIFFERS conflicts

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Assert the timestamp is available for ORIGN_DIFFERS conflicts
Date: 2026-01-21 05:22:41
Message-ID: TY7PR01MB14554B5E79AB1E535236ED997F596A@TY7PR01MB14554.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Hackers,

This is a fork from [1].

While constructing a conflict message, CT_UPDATE_ORIGIN_DIFFERS and
CT_DELETE_ORIGIN_DIFFERS assumes that timestamp for the local commit is always
available. Actually, it's valid because they can be detected only with
track_commit_timestamp, but source code does not describe anything for it.
PSA the patch to add Assert() or it.

[1]: https://www.postgresql.org/message-id/TY7PR01MB145540C10F511D9AF40CCB395F58DA%40TY7PR01MB14554.jpnprd01.prod.outlook.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
0001-Add-Assert-for-UPDATE-DELETE-_ORIGIN_DIFFERS.patch application/octet-stream 1.8 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-01-21 05:29:30 Re: docs: clarify ALTER TABLE behavior on partitioned tables
Previous Message jian he 2026-01-21 05:10:20 Re: support ALTER COLUMN SET EXPRESSION over virtual generated column with check constraint