Quick Links

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:31
Message-ID:	E1jleNH-0005OF-51@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
------
REL9_5_STABLE

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

	From	Date	Subject
Next Message	Peter Geoghegan	2020-06-17 22:24:22	pgsql: Fix nbtree.h dedup state comment.
Previous Message	Andres Freund	2020-06-17 20:09:28	pgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks are