diff options
| author | Nathan Bossart <nathan@postgresql.org> | 2024-06-05 15:32:47 -0500 |
|---|---|---|
| committer | Nathan Bossart <nathan@postgresql.org> | 2024-06-05 15:32:47 -0500 |
| commit | 030ea3961f26c602929c3b277d2f4e5f9fd4bd87 (patch) | |
| tree | 98ce62839550f9f1f3478d566a75b56f57290dfc | |
| parent | 1488dee08c4aa5b92a4cde66eb69b3e78e80a6d8 (diff) | |
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.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 655113fc553..430a90e9c1a 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. |