pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are
Date
Msg-id E1jleNE-0005Ne-IZ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
spinlock emulation: Fix bug when more than INT_MAX spinlocks are initialized.

Once the counter goes negative we ended up with spinlocks that errored
out on first use (due to check in tas_sema).

Author: Andres Freund
Reviewed-By: Robert Haas
Discussion: https://postgr.es/m/20200606023103.avzrctgv7476xj7i@alap3.anarazel.de
Backpatch: 9.5-

Branch
------
REL9_6_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/660622053419fbb776c7218f2110500b3b034b35

Modified Files
--------------
src/backend/storage/lmgr/spin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are
Next
From: Andres Freund
Date:
Subject: pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are