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
This commit is contained in:
Amit Kapila 2023-07-19 08:11:44 +05:30
parent 137b131d6f
commit 961cf5c905
1 changed files with 13 additions and 0 deletions

View File

@ -1622,6 +1622,19 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
parameter of <command>CREATE PUBLICATION</command>).
</para>
</listitem>
<listitem>
<para>
When using
<link linkend="sql-altertable-replica-identity-full"><literal>REPLICA IDENTITY FULL</literal></link>
on published tables, it is important to note that the <literal>UPDATE</literal>
and <literal>DELETE</literal> 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.
</para>
</listitem>
</itemizedlist>
</sect1>