Assert the timestamp is available for ORIGN_DIFFERS conflicts - Mailing list 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