pgsql: Document a few caveats in synchronous logical replication.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Document a few caveats in synchronous logical replication.
Date: 2021-06-17 06:25:16
Message-ID: E1ltlSm-0006bg-6h@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9f7bba2629cf3413638936d0376bb50403144332

Modified Files
--------------
doc/src/sgml/logicaldecoding.sgml | 76 +++++++++++++++++++++++++++++----------
1 file changed, 57 insertions(+), 19 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-06-17 07:05:07 pgsql: Fix subtransaction test for Python 3.10
Previous Message Michael Paquier 2021-06-17 02:58:38 pgsql: Detect unused steps in isolation specs and do some cleanup