From 38052a9dbc90305b8f1fa5b87cbd7099778e66ab Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 6 Sep 2011 11:08:35 -0400 Subject: [PATCH] Properly document semphore requirements by accounting for worker processes. Backpatch to 9.1 and 9.0. Submitted by Anton Yuzhaninov, confirmed by Robert Haas --- doc/src/sgml/runtime.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 01599af5c5c..d11c5bc8cfc 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -597,13 +597,13 @@ psql: could not connect to server: No such file or directory SEMMNI Maximum number of semaphore identifiers (i.e., sets) - at least ceil((max_connections + autovacuum_max_workers) / 16) + at least ceil((max_connections + autovacuum_max_workers + 4) / 16) SEMMNS Maximum number of semaphores system-wide - ceil((max_connections + autovacuum_max_workers) / 16) * 17 plus room for other applications + ceil((max_connections + autovacuum_max_workers + 4) / 16) * 17 plus room for other applications @@ -678,7 +678,7 @@ psql: could not connect to server: No such file or directory linkend="sysvipc-parameters">). The parameter SEMMNI determines the limit on the number of semaphore sets that can exist on the system at one time. Hence this parameter must be at - least ceil((max_connections + autovacuum_max_workers) / 16). + least ceil((max_connections + autovacuum_max_workers + 4) / 16). Lowering the number of allowed connections is a temporary workaround for failures, which are usually confusingly worded No space -- 2.47.2