pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are
Date: 2020-06-17 20:09:18
Message-ID: E1jleN4-0005M2-AH@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/276bdc93924afb2bd793627f49a9e7edd4172b63

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

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2020-06-17 20:09:20 pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are
Previous Message Andres Freund 2020-06-17 20:09:15 pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are