From c327b27e01bb2f5ab290d4b70fa990d328d84f13 Mon Sep 17 00:00:00 2001 From: Hou Zhijie Date: Tue, 13 Aug 2024 16:08:36 +0800 Subject: [PATCH v19 1/2] Doc: explain the log format of logical replication conflict This commit adds a detailed explanation of the log format for logical replication conflicts to the documentation. It aims to help users better understand conflict logs. --- doc/src/sgml/logical-replication.sgml | 69 +++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 885a2d70ae..8cbd8624a5 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -1666,6 +1666,75 @@ test_sub=# SELECT * FROM t1 ORDER BY id; log. + + The log format for logical replication conflicts is as follows: + +LOG: conflict detected on relation "schemaname.tablename": conflict=conflict_type +DETAIL: detailed explaination. +Key (column_name, ...)=(column_name, ...); existing local tuple (column_name, ...)=(column_name, ...); remote tuple (column_name, ...)=(column_name, ...); replica identity (column_name, ...)=(column_name, ...). + + The log provides the following information: + + + + The LOG line includes the name of the local relation + involved in the conflict and the conflict_type (e.g., + insert_exists, update_exists). + + + + + + The origin, transaction ID, and commit timestamp of the transaction that + modified the existing local tuple, if available, are included in the + detailed explanation section of the first sentence in + the DETAIL line. + + + + + + The key section in the second sentence of the + DETAIL line includes the key values of the tuple that + already exists in the local relation for insert_exists + or update_exists conflicts. + + + + + + The existing local tuple section in the second + sentence of the DETAIL line includes the local tuple + if its origin differs from the remote tuple in cases of + update_differ or delete_differ + conflicts, or if the key value conflicts with the remote tuple in cases + of insert_exists or update_exists + conflicts. + + + + + + The remote tuple section of the second sentence in the + DETAIL line includes the new tuple from the remote + insert or update operation that caused the conflict. Note that for an + update operation, the column value of the new tuple may be NULL if the + value is unchanged. + + + + + + The replica identity section of the second sentence in + the DETAIL line includes the replica identity key + values that used to search for the existing local tuple to be updated or + deleted. This may include the full tuple value if the local relation is + marked with REPLICA IDENTITY FULL. + + + + + Logical replication operations are performed with the privileges of the role which owns the subscription. Permissions failures on target tables will -- 2.30.0.windows.2