diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index b876758..acb9ece 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -1129,6 +1129,22 @@ OutputPluginWrite(ctx, true);
+ User has performed PREPARE TRANSACTION after LOCK
+ command on pg_class and logical decoding of published table
+ in a same transaction.
+
+
+
+
+
+ CLUSTERpg_trigger and
+ PREPARE TRANSACTION can cause a deadlock, if any published table have
+ a trigger and any operations that are decoded are conducted.
+
+
+
+
+
Executing TRUNCATE on user_catalog_table can prevent output plugin
from taking a lock to the table, which leads to a deadlock.
@@ -1301,9 +1317,11 @@ stream_commit_cb(...); <-- commit of the streamed transaction
The logical replication solution that builds distributed two phase commit
using this feature can deadlock if the prepared transaction has locked
- [user] catalog tables exclusively. They need to inform users to not have
- locks on catalog tables (via explicit LOCK command) in
- such transactions.
+ [user] catalog tables exclusively. To avoid this users must refrain from
+ having locks on catalog tables (e.g. explicit LOCK command)
+ in such transactions.
+ (See Synchronous
+ Replication Support for Logical Decoding for the details.)