aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-04-18 13:33:07 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-04-18 13:33:07 -0400
commitc6a5b6677d5f12ccf3c2373117bf630ead30b798 (patch)
tree9be708515ae244671dac5454bb7394a384354b16
parente2c183ef808466ed20c2d7877b9c10e13c897e16 (diff)
downloadpostgresql-c6a5b6677d5f12ccf3c2373117bf630ead30b798.tar.gz
postgresql-c6a5b6677d5f12ccf3c2373117bf630ead30b798.zip
Further reduce the number of semaphores used under --disable-spinlocks.
Per discussion, there doesn't seem to be much value in having NUM_SPINLOCK_SEMAPHORES set to 1024: under any scenario where you are running more than a few backends concurrently, you really had better have a real spinlock implementation if you want tolerable performance. And 1024 semaphores is a sizable fraction of the system-wide SysV semaphore limit on many platforms. Therefore, reduce this setting's default value to 128 to make it less likely to cause out-of-semaphores problems.
-rw-r--r--src/include/pg_config_manual.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/pg_config_manual.h b/src/include/pg_config_manual.h
index e278fa07d3d..91fb134e96f 100644
--- a/src/include/pg_config_manual.h
+++ b/src/include/pg_config_manual.h
@@ -62,7 +62,7 @@
* may improve performance, but supplying a real spinlock implementation is
* probably far better.
*/
-#define NUM_SPINLOCK_SEMAPHORES 1024
+#define NUM_SPINLOCK_SEMAPHORES 128
/*
* When we have neither spinlocks nor atomic operations support we're