diff options
| author | Amit Kapila <akapila@postgresql.org> | 2023-07-19 08:11:44 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2023-07-19 08:11:44 +0530 |
| commit | 961cf5c9055ff5f689a06aafed3346146b3cee43 (patch) | |
| tree | 0de1ff604a0ad62fb5edfd6974817c688063371c | |
| parent | 137b131d6fbd29b4acf740aba3f74220faef2678 (diff) | |
| download | postgresql-961cf5c9055ff5f689a06aafed3346146b3cee43.tar.gz postgresql-961cf5c9055ff5f689a06aafed3346146b3cee43.zip | |
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
| -rw-r--r-- | doc/src/sgml/logical-replication.sgml | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index e71f4bac69c..fbf8ad669e4 100644 --- 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 <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> |