From 08f4ccf2b5403b84b15b14ddb26b529cb3c11c27 Mon Sep 17 00:00:00 2001 From: Mikhail Nikalayeu Date: Thu, 13 Nov 2025 03:11:11 +0100 Subject: [PATCH v1 2/2] update for pg19: documentation update to reflect issue described in https://commitfest.postgresql.org/patch/5151/ and https://www.postgresql.org/message-id/flat/CADzfLwXZVmbo11tFS_G2i+6TfFVwHU4VUUSeoqb+8UQfuoJs8A@mail.gmail.com --- doc/src/sgml/logical-replication.sgml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index e20c92d15f0..4c6ee9e9229 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -2236,7 +2236,8 @@ DETAIL: detailed_explanation. Due to some restrictions in implementation of conflict detection, logical replication may report incorrect conflict types in the server log and statistics. An update_origin_differs conflict - may be incorrectly reported as update_missing, and a + may be incorrectly reported as update_missing or + update_deleteddelete_origin_differs conflict may be incorrectly reported as delete_missing. In some cases such race condition may cause inconsistent behaviour, see @@ -2448,8 +2449,8 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER An UPDATE from the publisher not being applied, so the publisher's changes are lost while the subscriber's local changes - remain. In this case an update_missing conflict is - logged instead of update_origin_differs. This can + remain. In this case an update_missing or + conflict is logged instead of update_origin_differs. This can occur even when the subscriber's UPDATE modifies only columns that do not exist on the publisher, which might otherwise appear to be a safe operation. -- 2.43.0