v3_add_description.patch

application/octet-stream

Filename: v3_add_description.patch

Type: application/octet-stream

Part: 0

Message: RE: 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

Series: patch v3

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

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index c5de2040f7..357b8646e3 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1622,6 +1622,18 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
      parameter of <command>CREATE PUBLICATION</command>).
     </para>
    </listitem>
+
+   <listitem>
+    <para>
+     The <literal>UPDATE</literal> and <literal>DELETE</literal> operations
+     cannot be applied on subscriber for the published tables that specifies
+     <link linkend="sql-altertable-replica-identity-full"><literal>REPLICA IDENTITY FULL</literal></link>
+     but the table includes an attribute whose datatype is not an operator
+     class of Btree or Hash. To make it work, a primary key should be defined
+     on the subscriber table, or a different appropriate replica identity must
+     be specified.
+    </para>
+   </listitem>
   </itemizedlist>
  </sect1>