add_description.patch

application/octet-stream

Filename: add_description.patch

Type: application/octet-stream

Part: 0

Message: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →

Format: unified

File	+	−
doc/src/sgml/logical-replication.sgml	11	0

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index c5de2040f7..88f333ceb4 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1622,6 +1622,17 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
      parameter of <command>CREATE PUBLICATION</command>).
     </para>
    </listitem>
+
+   <listitem>
+    <para>
+     When <literal>REPLICA IDENTITY FULL</literal> is specified on publisher
+     and the published table has attributes which the datatype is not for
+     operator class of Btree, <literal>UPDATE</literal> and <literal>DELETE</literal>
+     operations cannot be replicated. To replicate them the primary key must be
+     defined on subscriber, or the appropriate replica identity must be
+     specified.
+    </para>
+   </listitem>
   </itemizedlist>
  </sect1>