Don't call elog() while holding spinlock.
authorFujii Masao <fujii@postgresql.org>
Tue, 2 Jun 2020 10:18:13 +0000 (19:18 +0900)
committerFujii Masao <fujii@postgresql.org>
Tue, 2 Jun 2020 10:21:04 +0000 (19:21 +0900)
commitcaa3c4242cf86322e2ed0c86199e6462a2c41565
tree37c398265073850ae31a63241b4465114f2dc1e0
parente641b2a995abfa0dd7039863e2597feb3abf2b1e
Don't call elog() while holding spinlock.

Previously UpdateSpillStats() called elog(DEBUG2) while holding
the spinlock even though the local variables that the elog() accesses
don't need to be protected by the lock. Since spinlocks are intended
for very short-term locks, they should not be used when calling
elog(DEBUG2). So this commit moves that elog() out of spinlock period.

Author: Kyotaro Horiguchi
Reviewed-by: Amit Kapila and Fujii Masao
Discussion: https://postgr.es/m/20200602.161518.1399689010416646074.horikyota.ntt@gmail.com
src/backend/replication/walsender.c