From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Drop slot's LWLock before returning from SaveSlotToPath() |
Date: | 2020-03-26 13:16:01 |
Message-ID: | E1jHSMb-00087I-3t@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Drop slot's LWLock before returning from SaveSlotToPath()
When SaveSlotToPath() is called with elevel=LOG, the early exits didn't
release the slot's io_in_progress_lock.
This could result in a walsender being stuck on the lock forever. A
possible way to get into this situation is if the offending code paths
are triggered in a low disk space situation.
Author: Pavan Deolasee <pavan(dot)deolasee(at)2ndquadrant(dot)com>
Reported-by: Craig Ringer <craig(at)2ndquadrant(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/56a138c5-de61-f553-7e8f-6789296de785%402ndquadrant.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/49bf81536e242f079bfbce6e8f95f53f18207dd5
Modified Files
--------------
src/backend/replication/slot.c | 10 ++++++++++
1 file changed, 10 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-26 13:50:11 | Re: pgsql: Provide a TLS init hook |
Previous Message | Andrew Dunstan | 2020-03-26 11:01:39 | Re: pgsql: Provide a TLS init hook |