From: Nathan Bossart <nathandbossart@gmail.com>
To: Imseih (AWS), Sami <simseih@amazon.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: problems with "Shared Memory and Semaphores" section of docs
Date: Mon, 3 Jun 2024 14:04:19 -0500
Message-ID: <Zl4TswfwPUZkHHfn@nathan> (raw)
In-Reply-To: <Zl363er4TUbOkJEf@nathan>
References: <20240517164452.GA1914161@nathanxps13>
<2463906.1715965795@sss.pgh.pa.us>
<20240517174837.GB1918496@nathanxps13>
<20240517192123.GA1933425@nathanxps13>
<ZkzyBOD-cX35wKuM@nathan>
<F4131F24-A20F-4A04-B1A6-60242A7C7A43@amazon.com>
<Zl363er4TUbOkJEf@nathan>
On Mon, Jun 03, 2024 at 12:18:21PM -0500, Nathan Bossart wrote:
> On Tue, May 21, 2024 at 11:15:14PM +0000, Imseih (AWS), Sami wrote:
>> As far as backpatching the present inconsistencies in the docs,
>> [0] looks good to me.
>
> Committed.
Of course, as soon as I committed this, I noticed another missing reference
to max_wal_senders in the paragraph about POSIX semaphores. I plan to
commit/back-patch the attached patch within the next couple days.
--
nathan
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgmlindex 883a849e6f..2f7c618886 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.
Attachments:
[text/plain] add_missing_max_wal_sender_reference.patch (903B, ../Zl4TswfwPUZkHHfn@nathan/2-add_missing_max_wal_sender_reference.patch)
download | inline diff:diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgmlindex 883a849e6f..2f7c618886 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nathandbossart@gmail.com, simseih@amazon.com, tgl@sss.pgh.pa.us, pryzby@telsasoft.com
Subject: Re: problems with "Shared Memory and Semaphores" section of docs
In-Reply-To: <Zl4TswfwPUZkHHfn@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox