Fix --disable-spinlocks in 9.2 and 9.3 branches.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 18 Apr 2016 17:19:52 +0000 (13:19 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 18 Apr 2016 17:19:52 +0000 (13:19 -0400)
commit37f30b2510525155f4f1f94288a015163689cc69
treefc623aace68895adc020cefcc8c0ebc2025d2f2d
parent9008922bf727ba4337ed26b5c07df7f1d5f1548b
Fix --disable-spinlocks in 9.2 and 9.3 branches.

My back-patch of the 9.4-era commit 44cd47c1d49655c5 into 9.2 and 9.3 fixed
HPPA builds as expected, but it broke --disable-spinlocks builds, because
the dummy spinlock is initialized before the underlying semaphore
infrastructure is alive.  In 9.4 and up this works because of commit
daa7527afc227443, which decoupled initialization of an slock_t variable
from access to the actual system semaphore object.  The best solution
seems to be to back-port that patch, which should be a net win anyway
because it improves the usability of --disable-spinlocks builds in the
older branches; and it's been out long enough now to not be worrisome
from a stability perspective.
src/backend/postmaster/postmaster.c
src/backend/storage/ipc/ipci.c
src/backend/storage/ipc/shmem.c
src/backend/storage/lmgr/spin.c
src/include/pg_config_manual.h
src/include/storage/s_lock.h
src/include/storage/spin.h