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 1thwUL-008tvW-RT for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2025 20:04:09 +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 1thwUK-00F7Sk-Gm for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Feb 2025 20:04:08 +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 1thwUK-00F7PM-6p for pgsql-hackers@lists.postgresql.org; Tue, 11 Feb 2025 20:04:08 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1thwUH-000JKI-1d for pgsql-hackers@postgresql.org; Tue, 11 Feb 2025 20:04:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 51BK42ng3208743; Tue, 11 Feb 2025 15:04:02 -0500 From: Tom Lane To: Andres Freund cc: Jelte Fennema-Nio , PostgreSQL-development Subject: Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup In-reply-to: <4qacnswlyykgj6p2gon4pvv7r2cb4adtedguer6pmaktr4xdve@om6ej7u4qw7p> References: <4qacnswlyykgj6p2gon4pvv7r2cb4adtedguer6pmaktr4xdve@om6ej7u4qw7p> Comments: In-reply-to Andres Freund message dated "Tue, 11 Feb 2025 14:42:21 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3208741.1739304242.1@sss.pgh.pa.us> Date: Tue, 11 Feb 2025 15:04:02 -0500 Message-ID: <3208742.1739304242@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > I don't see a downside to just increasing the soft limit for > pgbench. Agreed, that end of the patch seems relatively harmless. regards, tom lane