diff options
| -rw-r--r-- | doc/src/sgml/logicaldecoding.sgml | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 4c2ca12445e..35202a789cf 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -754,16 +754,18 @@ OutputPluginWrite(ctx, true); <para> In synchronous replication setup, a deadlock can happen, if the transaction - has locked [user] catalog tables exclusively. This is because logical decoding of - transactions can lock catalog tables to access them. To avoid this users - must refrain from taking an exclusive lock on [user] catalog tables. This can - happen in the following ways: + has locked [user] catalog tables exclusively. See + <xref linkend="logicaldecoding-capabilities"/> for information on user + catalog tables. This is because logical decoding of transactions can lock + catalog tables to access them. To avoid this users must refrain from taking + an exclusive lock on [user] catalog tables. This can happen in the following + ways: <itemizedlist> <listitem> <para> Issuing an explicit <command>LOCK</command> on <structname>pg_class</structname> - (or any other catalog table) in a transaction. + in a transaction. </para> </listitem> @@ -781,6 +783,10 @@ OutputPluginWrite(ctx, true); </para> </listitem> </itemizedlist> + + Note that these commands that can cause deadlock apply to not only explicitly + indicated system catalog tables above but also to any other [user] catalog + table. </para> </sect2> </sect1> |