mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03:00
Remove --disable-spinlocks.
A later change will require atomic support, so it wouldn't make sense for a hypothetical new system not to be able to implement spinlocks. Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> (concept, not the patch) Reviewed-by: Andres Freund <andres@anarazel.de> (concept, not the patch) Discussion: https://postgr.es/m/3351991.1697728588%40sss.pgh.pa.us
This commit is contained in:
13
configure.ac
13
configure.ac
@ -186,12 +186,6 @@ PGAC_ARG_BOOL(enable, rpath, yes,
|
||||
[do not embed shared library search path in executables])
|
||||
AC_SUBST(enable_rpath)
|
||||
|
||||
#
|
||||
# Spinlocks
|
||||
#
|
||||
PGAC_ARG_BOOL(enable, spinlocks, yes,
|
||||
[do not use spinlocks])
|
||||
|
||||
#
|
||||
# Atomic operations
|
||||
#
|
||||
@ -1296,13 +1290,6 @@ failure. It is possible the compiler isn't looking in the proper directory.
|
||||
Use --without-zlib to disable zlib support.])])
|
||||
fi
|
||||
|
||||
if test "$enable_spinlocks" = yes; then
|
||||
AC_DEFINE(HAVE_SPINLOCKS, 1, [Define to 1 if you have spinlocks.])
|
||||
else
|
||||
AC_MSG_WARN([
|
||||
*** Not using spinlocks will cause poor performance.])
|
||||
fi
|
||||
|
||||
if test "$enable_atomics" = yes; then
|
||||
AC_DEFINE(HAVE_ATOMICS, 1, [Define to 1 if you want to use atomics if available.])
|
||||
else
|
||||
|
Reference in New Issue
Block a user