From d3a4d51db0b83e4456b6b5738fdc7f1a23bb6fce Mon Sep 17 00:00:00 2001
From: Shveta Malik <shveta.malik@gmail.com>
Date: Thu, 15 Oct 2026 11:23:25 +0530
Subject: [PATCH] origin doc improvement

---
 doc/src/sgml/logical-replication.sgml | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 0d88cbfd4fd..0a79e6e6ca1 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -2389,9 +2389,13 @@ DETAIL:  <replaceable class="parameter">detailed_explanation</replaceable>[: <re
          An array of JSON objects representing the state of existing local
          row(s) that caused the conflict. Each object includes the local
          transaction ID (<literal>xid</literal>), commit timestamp
-         (<literal>commit_ts</literal>), and origin (<literal>origin</literal>).
-         This is <literal>NULL</literal> if there are no local conflicting rows
-         (e.g., in <literal>update_missing</literal> and
+         (<literal>commit_ts</literal>), and the name of the replication
+         origin that last modified the row (<literal>origin</literal>).
+         The <literal>origin</literal> field is <literal>NULL</literal> if
+         the transaction had no replication origin set or if that origin has
+         since been dropped. The column itself is <literal>NULL</literal>
+         if there are no local conflicting rows (e.g., in
+         <literal>update_missing</literal> and
          <literal>delete_missing</literal> conflicts).
         </entry>
        </row>
-- 
2.34.1