Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commita502d6b

Browse files
Amit Kapilapull[bot]
Amit Kapila
authored andcommitted
Doc: Update the logical replication restriction w.r.t Replica Identity Full.
Author: Kuroda HayatoReviewed-by: Peter Smith, Onder Kalaci, Sergei Kornilov, Amit KapilaDiscussion:https://postgr.es/m/TYAPR01MB58662174ED62648E0D611194F530A@TYAPR01MB5866.jpnprd01.prod.outlook.com
1 parent503bb9e commita502d6b

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

‎doc/src/sgml/logical-replication.sgml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1622,6 +1622,19 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
16221622
parameter of <command>CREATE PUBLICATION</command>).
16231623
</para>
16241624
</listitem>
1625+
1626+
<listitem>
1627+
<para>
1628+
When using
1629+
<link linkend="sql-altertable-replica-identity-full"><literal>REPLICA IDENTITY FULL</literal></link>
1630+
on published tables, it is important to note that the <literal>UPDATE</literal>
1631+
and <literal>DELETE</literal> operations cannot be applied to subscribers
1632+
if the tables include attributes with datatypes (such as point or box)
1633+
that do not have a default operator class for B-tree or Hash. However,
1634+
this limitation can be overcome by ensuring that the table has a primary
1635+
key or replica identity defined for it.
1636+
</para>
1637+
</listitem>
16251638
</itemizedlist>
16261639
</sect1>
16271640

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp