pgsql: Fix oversight from 9e149c8 with spin-lock handling

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix oversight from 9e149c8 with spin-lock handling
Date: 2018-06-11 21:53:50
Message-ID: E1fSUl4-0005Nu-0j@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix oversight from 9e149c8 with spin-lock handling

Calling an external function while a pin-lock is held is a bad idea as
those are designed to be short-lived. The stress of a first commit into
a large git history may contribute to that.

Reported-by: Andres Freund
Discussion: https://postgr.es/m/20180611164952.vmxdpdpirdtkdsz6@alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f8795d2ec8632a7242896e0f8322d13bfe922512

Modified Files
--------------
src/backend/replication/slot.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2018-06-11 23:16:34 Re: [COMMITTERS] pgsql: Logical replication
Previous Message Michael Paquier 2018-06-11 21:47:27 Re: pgsql: Fix and document lock handling for in-memory replication slot da