From b669b24bde5eb541530b9f76dceb232f618c5815 Mon Sep 17 00:00:00 2001
From: Zhijie Hou <houzj.fnst@fujitsu.com>
Date: Thu, 20 Aug 2026 10:35:08 +0800
Subject: [PATCH v70 3/3] Doc: note virtual generated columns in the conflict
 log table

Virtual generated columns are never sent by the publisher and have no
stored value on the subscriber, so their values appear as null in the
JSON columns (remote_tuple, local_conflicts) of the conflict log table,
whereas the server log shows them with the constant value "virtual".
Document this difference.
---
 doc/src/sgml/logical-replication.sgml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 0d9892764df..5d2efbfe713 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -2286,6 +2286,13 @@ Included in publications:
      and the associated local conflict details (<literal>local_conflicts</literal>), is stored in
      <type>JSON</type> formats for flexible querying and analysis.
     </para>
+
+    <para>
+     Note that virtual generated column values appear as
+     <literal>null</literal> in these JSON columns, because such columns have no
+     stored value on the subscriber. In the server log, such columns are instead
+     shown with the constant value <literal>virtual</literal>.
+    </para>
    </sect3>
 
    <sect3 id="logical-replication-conflict-file-based-logging">
-- 
2.43.0