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
commit78fe33742dccc23d4b8a4a1cc7a311e7be0403d1 (patch)
tree2c9c3ab0003d00ead5f68b52320ca8eef3700661
parent30487423c8296ea448f4deb56f5caec46111b763 (diff)
downloadpostgresql-78fe33742dccc23d4b8a4a1cc7a311e7be0403d1.tar.gz
postgresql-78fe33742dccc23d4b8a4a1cc7a311e7be0403d1.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 2f660e288e0..33f0552edd0 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -858,7 +858,8 @@ psql: could not connect to server: No such file or directory
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.