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 1u9lxj-0069R5-BL for pgsql-committers@arkaria.postgresql.org; Tue, 29 Apr 2025 14:29:31 +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 1u9lxh-007eUc-Ad for pgsql-committers@arkaria.postgresql.org; Tue, 29 Apr 2025 14:29:30 +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 1u9lxh-007eUU-3O for pgsql-committers@lists.postgresql.org; Tue, 29 Apr 2025 14:29:30 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u9lxg-000CHY-0m for pgsql-committers@lists.postgresql.org; Tue, 29 Apr 2025 14:29:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=mq5H5zGVA267XULFJ4vWwGmAGaSMgLBkouvQQfIaGwQ=; b=Fuvde lM1pS8+xEyshzmdtItcaTttuz1kc+5l8473Oqyb7atYgGuCBSU/OqMJ4rveQ+je3K0nAww4ih+iC5 9M7Bi3rvbCvOWGkPCW1+mXY2GhVRKcao86qju2KzDVdrU+l4tTd4EcCL20d+m+4M9+pYRTsxa02ns Q8z+UM5y10ojC2ODxQOVp22dT+wQrSE7nZmBX4AyvKV6Cs4F0V+K7s8gSSSuHHRXvpbMarek+My2p /6gD5Z56MQNhYx8YOQ2ghPW1qV0tY9q0yDnSaF3ByzKp+xMojWX6dDkaAyKb+lD7JpCQr8RXasPnB sAqJ7Nohb6epqLYqNI4BlSYoLiRTA==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1u9lxf-00FnU4-0H; Tue, 29 Apr 2025 10:29:27 -0400 Date: Tue, 29 Apr 2025 10:29:27 -0400 From: Bruce Momjian To: Andres Freund Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: doc: clarify new behavior of max_files_per_process Message-ID: References: <5yqochswkulckuzzrwgv2nqdrfh4k4coc4uwq4lvgzkfwnbjbd@46igbiwjabn2> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 29, 2025 at 10:26:50AM -0400, Bruce Momjian wrote: > On Tue, Apr 29, 2025 at 09:52:03AM -0400, Andres Freund wrote: > > Hi, > > > > On 2025-04-29 13:45:44 +0000, Bruce Momjian wrote: > > > doc: clarify new behavior of max_files_per_process > > > > I don't think this really is an improvement - if postmaster is called with a > > bunch of files already opened, they aren't opened by postmaster, but still are > > ignored... > > Okay, I was more objecting to the text that wasn't clear; it was: > > Sets the maximum number of open files each server subprocess is > allowed to open simultaneously, in addition to the files already > open in postmaster. The default is one thousand files. > > The "in addition" wasn't clear to me. I could read it as "adding" the > postmaster file descriptors. I changed it now to: > > Sets the maximum number of open files each server subprocess is > allowed to open simultaneously; files opened in the postmaster are > not counted toward this limit. The default is one thousand files. I ended up preserving your "already" too: Sets the maximum number of open files each server subprocess is allowed to open simultaneously; files already opened in the postmaster are not counted toward this limit. The default is one thousand files. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.