aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2024-06-05 15:32:47 -0500
committerNathan Bossart <nathan@postgresql.org>2024-06-05 15:32:47 -0500
commitbb8425491cb7d5c760913761bf13644a7e86f58f (patch)
treefc81ff41c00f48ae4c7ed47a3bd8e9f9fb7fc04f
parent89ef2aedae448cc51cd7bf7c81d56a08d1da7467 (diff)
downloadpostgresql-bb8425491cb7d5c760913761bf13644a7e86f58f.tar.gz
postgresql-bb8425491cb7d5c760913761bf13644a7e86f58f.zip
Fix documentation for POSIX semaphores.
The documentation for POSIX semaphores is missing a reference to max_wal_senders. This commit fixes that in the same way that commit 4ebe51a5fb fixed the same issue in the documentation for System V semaphores. Discussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13 Backpatch-through: 12
-rw-r--r--doc/src/sgml/runtime.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 9a028d6a73a..24ea97ff0d1 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -884,7 +884,8 @@ psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such
When using POSIX semaphores, the number of semaphores needed is the
same as for System V, that is one semaphore per allowed connection
(<xref linkend="guc-max-connections"/>), allowed autovacuum worker process
- (<xref linkend="guc-autovacuum-max-workers"/>) and allowed background
+ (<xref linkend="guc-autovacuum-max-workers"/>), allowed WAL sender process
+ (<xref linkend="guc-max-wal-senders"/>), and allowed background
process (<xref linkend="guc-max-worker-processes"/>).
On the platforms where this option is preferred, there is no specific
kernel limit on the number of POSIX semaphores.