]> 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:10:56 +0000 (10:40 +0530)
committerAmit Kapila <akapila@postgresql.org>
Thu, 17 Jun 2021 05:10:56 +0000 (10:40 +0530)
commiteb231dbd80d2318e27e9b4d0aa72696de6e6b32f
tree6dd439cd303f3d791338ee5efbb883e04e237de1
parent96f3661e4540db1f45709c5f098aeecc6e9df271
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