pgsql: Fix deadlock with LWLockAcquireWithVar and LWLockWaitForVar. - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Fix deadlock with LWLockAcquireWithVar and LWLockWaitForVar.
Date
Msg-id E1XdwJT-0004sl-Ur@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix deadlock with LWLockAcquireWithVar and LWLockWaitForVar.

LWLockRelease should release all backends waiting with LWLockWaitForVar,
even when another backend has already been woken up to acquire the lock,
i.e. when releaseOK is false. LWLockWaitForVar can return as soon as the
protected value changes, even if the other backend will acquire the lock.
Fix that by resetting releaseOK to true in LWLockWaitForVar, whenever
adding itself to the wait queue.

This should fix the bug reported by MauMau, where the system occasionally
hangs when there is a lot of concurrent WAL activity and a checkpoint.
Backpatch to 9.4, where this code was added.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/4dbc7606cfc8188646a2e302ef5e6a5ec3c962af

Modified Files
--------------
src/backend/storage/lmgr/lwlock.c |    6 ++++++
1 file changed, 6 insertions(+)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Don't let protected variable access to be reordered after spinlo
Next
From: Alvaro Herrera
Date:
Subject: pgsql: pg_dump: Reduce use of global variables