|
SEMMNI
Maximum number of semaphore identifiers (i.e., sets)
- at least ceil((max_connections + autovacuum_max_workers + max_wal_senders + max_worker_processes + 5) / 16) plus room for other applications
+ at least ceil((max_connections + autovacuum_max_workers + max_wal_senders + max_worker_processes + 7) / 16) plus room for other applications
|
SEMMNS
Maximum number of semaphores system-wide
- ceil((max_connections + autovacuum_max_workers + max_wal_senders + max_worker_processes + 5) / 16) * 17 plus room for other applications
+ ceil((max_connections + autovacuum_max_workers + max_wal_senders + max_worker_processes + 7) / 16) * 17 plus room for other applications
|
When using System V semaphores,
PostgreSQL uses one semaphore per allowed connection
(), allowed autovacuum worker process
- () and allowed background
+ (), allowed WAL sender process
+ (), and allowed background
process (), in sets of 16.
Each such set will
also contain a 17th semaphore which contains a magic
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 + max_wal_senders + max_worker_processes + 5) / 16).
+ least ceil((max_connections + autovacuum_max_workers + max_wal_senders + max_worker_processes + 7) / 16).
Lowering the number
of allowed connections is a temporary workaround for failures,
which are usually confusingly worded No space