Doc: Update the logical replication restriction w.r.t Replica Identity Full.

Author: Kuroda Hayato
Reviewed-by: Peter Smith, Onder Kalaci, Sergei Kornilov, Amit Kapila
Discussion: https://postgr.es/m/TYAPR01MB58662174ED62648E0D611194F530A@TYAPR01MB5866.jpnprd01.prod.outlook.com

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index e71f4bac69cada60d8282e8a65ccfc5553f3008e..fbf8ad669e4fcad0cca99d74d8bfcff466ac4cec 100644 (file)
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1622,6 +1622,19 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
      parameter of CREATE PUBLICATION).
     
    
+
+   
+    
+     When using
+     REPLICA IDENTITY FULL
+     on published tables, it is important to note that the UPDATE
+     and DELETE operations cannot be applied to subscribers
+     if the tables include attributes with datatypes (such as point or box)
+     that do not have a default operator class for B-tree or Hash. However,
+     this limitation can be overcome by ensuring that the table has a primary
+     key or replica identity defined for it.
+    
+