Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sECyo-000DdD-PB for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Jun 2024 19:04:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sECyo-00CJY1-9j for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Jun 2024 19:04:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sECyn-00CJXt-Vq for pgsql-hackers@lists.postgresql.org; Mon, 03 Jun 2024 19:04:26 +0000 Received: from mail-il1-x12e.google.com ([2607:f8b0:4864:20::12e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sECyl-002Ajx-Bb for pgsql-hackers@postgresql.org; Mon, 03 Jun 2024 19:04:25 +0000 Received: by mail-il1-x12e.google.com with SMTP id e9e14a558f8ab-3737b70a74aso15192805ab.0 for ; Mon, 03 Jun 2024 12:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717441462; x=1718046262; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=+rBedQUz2ybiXUxHQGnJ6UO6Sqah+iuKAaLXMYJ7EEs=; b=I1stvFA/5+dlLxr3YUPMPDjvl7VNy8Yz4Otk2EmUok7cDlyL8HJCGzLsp19AIGZhSx NRAfINi4aYZ0vzI/zK191u3RIHSJS6xSu4tDwW1WF/W2paDdKK2NsuoRWF3DF20SAaNn zxcbJ3p23c79MmQFAj4ruPvpgddhP6t5xf4cDBDpIjlmph668sdaRkhYmqQKXMMvo5Om zUSIE/qipbNTRF4LRZ6yk1XuM1ZM+PD4vPD+ZvjksEsQ+2TqBahHfm/uvn5GcajVCQWQ PzdsE2Gem8Z8VBQl1VeambQKmbEEdtOSX/b/+DprZ7iEvE6F4bEUE++uOmvYTiJWedGK AfvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717441462; x=1718046262; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=+rBedQUz2ybiXUxHQGnJ6UO6Sqah+iuKAaLXMYJ7EEs=; b=a71xrgQ2GcbmMlgfogqeAVGzJ74jleRpvmR1jcu2QyzwqE/DaY1rVRfaiSFaLy5VOJ oV8myTR4IiV1lruJAprdabU90KOp5NXd8I1E7a/QZgscqVs8t5Dj3B85/y9tpbUUvOQE 1hqMjk6n+Cl94vIYmIv16ekxF0gpRT6d+TRCtqDYVhR0tVDVBZDe1QRWsSGIWkRPMq6c LKyMXFKaUlBTskKnL+7xE5euR7T7By0apqjzQySV6hNiZ6YIuX0HSroz+HZHIUzYFjN1 2KnRrxuvZ4je+j9Ff5oJJbAsg0MzSZtv3xrcSwfohOcI2hV7E0iG3h+dOizwAqDqgbNZ QyEA== X-Forwarded-Encrypted: i=1; AJvYcCVuR+9r8Gpvnv/q2XNKducVIADuogumaX0ztB5AA25iKjWLSAkPhw52t/BXTQ1vbLnRVbEVMWea6CIfguhcV7LD56MFw8CExme7j7pz X-Gm-Message-State: AOJu0YwqPbieXtQVf8fhjBDF6S5/+9Ne/H1SzvTrgl8yCq4hq673Fj5y Vu38xrz+463eb1XhEr/bMfYTjqs9wCqgOgiuwTO7dggLbphXTKQn X-Google-Smtp-Source: AGHT+IHhY0hdxiFL6vZAOqZYLAwagHMpprA4IjsL1VlnqqR6Jh5m7CId0RX/TZXzkqWm6U4xPAy/XQ== X-Received: by 2002:a05:6e02:1fe6:b0:374:8172:c281 with SMTP id e9e14a558f8ab-374a84ede79mr4696825ab.8.1717441461920; Mon, 03 Jun 2024 12:04:21 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-3749544a53dsm11629945ab.44.2024.06.03.12.04.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Jun 2024 12:04:21 -0700 (PDT) Date: Mon, 3 Jun 2024 14:04:19 -0500 From: Nathan Bossart To: "Imseih (AWS), Sami" Cc: Tom Lane , Justin Pryzby , "pgsql-hackers@postgresql.org" Subject: Re: problems with "Shared Memory and Semaphores" section of docs Message-ID: References: <20240517164452.GA1914161@nathanxps13> <2463906.1715965795@sss.pgh.pa.us> <20240517174837.GB1918496@nathanxps13> <20240517192123.GA1933425@nathanxps13> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="vn2DWUXFU3EakOwp" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --vn2DWUXFU3EakOwp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --vn2DWUXFU3EakOwp Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="add_missing_max_wal_sender_reference.patch" diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 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 (), allowed autovacuum worker process - () and allowed background + (), allowed WAL sender process + (), and allowed background process (). On the platforms where this option is preferred, there is no specific kernel limit on the number of POSIX semaphores. --vn2DWUXFU3EakOwp--