pgsql: Fix instance of elog() called while holding a spinlock

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix instance of elog() called while holding a spinlock
Date: 2020-06-04 01:22:26
Message-ID: E1jgeaQ-0003WB-8o@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix instance of elog() called while holding a spinlock

This broke the project rule to not call any complex code while a
spinlock is held. Issue introduced by b89e151.

Discussion: https://postgr.es/m/20200602.161518.1399689010416646074.horikyota.ntt@gmail.com
Backpatch-through: 9.5

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/03aa25b6e34b5f5184cfd0df71f1096c66523b72

Modified Files
--------------
src/backend/replication/logical/logical.c | 24 ++++++++++++++++--------
1 file changed, 16 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-06-04 04:09:31 pgsql: Fix comment in be-secure-openssl.c
Previous Message Tom Lane 2020-06-03 16:36:56 pgsql: Don't call palloc() while holding a spinlock, either.