]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Document a few caveats in synchronous logical replication.
authorAmit Kapila <akapila@postgresql.org>
Thu, 17 Jun 2021 05:29:11 +0000 (10:59 +0530)
committerAmit Kapila <akapila@postgresql.org>
Thu, 17 Jun 2021 05:29:11 +0000 (10:59 +0530)
commit5a456034b84e9147e648d512c66f2b2a50bad9f3
treeea07ce7564c6e3d58c5781c2d739e0cfd5cc1abb
parent8f32299424d90b0dab792bf96a5b0e3a62cc63da
Document a few caveats in synchronous logical replication.

In a synchronous logical setup, locking [user] catalog tables can cause
deadlock. This is because logical decoding of transactions can lock
catalog tables to access them so exclusively locking those in transactions
can lead to deadlock. To avoid this users must refrain from having
exclusive locks on catalog tables.

Author: Takamichi Osumi
Reviewed-by: Vignesh C, Amit Kapila
Backpatch-through: 9.6
Discussion: https://www.postgresql.org/message-id/20210222222847.tpnb6eg3yiykzpky%40alap3.anarazel.de
doc/src/sgml/logicaldecoding.sgml