diff options
Diffstat (limited to 'doc/src/sgml/logical-replication.sgml')
| -rw-r--r-- | doc/src/sgml/logical-replication.sgml | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index fcac55aefe6..a0761cfee3f 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -1804,6 +1804,22 @@ Publications: </para> </listitem> </varlistentry> + <varlistentry id="conflict-update-deleted" xreflabel="update_deleted"> + <term><literal>update_deleted</literal></term> + <listitem> + <para> + The tuple to be updated was concurrently deleted by another origin. The + update will simply be skipped in this scenario. Note that this conflict + can only be detected when + <link linkend="guc-track-commit-timestamp"><varname>track_commit_timestamp</varname></link> + and <link linkend="sql-createsubscription-params-with-retain-dead-tuples"><literal>retain_dead_tuples</literal></link> + are enabled. Note that if a tuple cannot be found due to the table being + truncated, only a <literal>update_missing</literal> conflict will + arise. Additionally, if the tuple was deleted by the same origin, an + <literal>update_missing</literal> conflict will arise. + </para> + </listitem> + </varlistentry> <varlistentry id="conflict-update-missing" xreflabel="update_missing"> <term><literal>update_missing</literal></term> <listitem> |