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.96) (envelope-from ) id 1vXqH7-007JQs-0Z for pgsql-docs@arkaria.postgresql.org; Tue, 23 Dec 2025 00:29:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vXqH5-00GqD7-2y for pgsql-docs@arkaria.postgresql.org; Tue, 23 Dec 2025 00:29:16 +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.96) (envelope-from ) id 1vXqH5-00GqCz-2C for pgsql-docs@lists.postgresql.org; Tue, 23 Dec 2025 00:29:16 +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 1vXqH3-002Ch9-2T for pgsql-docs@lists.postgresql.org; Tue, 23 Dec 2025 00:29:16 +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 5BN0TAfC651984; Mon, 22 Dec 2025 19:29:10 -0500 From: Tom Lane To: Bruce Momjian cc: colinthart@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Which parameters are only used on startup? In-reply-to: References: <176414965817.802.9539749613450037479@wrigleys.postgresql.org> Comments: In-reply-to Bruce Momjian message dated "Mon, 22 Dec 2025 19:14:31 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <651982.1766449750.1@sss.pgh.pa.us> Date: Mon, 22 Dec 2025 19:29:10 -0500 Message-ID: <651983.1766449750@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: > On Wed, Nov 26, 2025 at 09:34:18AM +0000, PG Doc comments form wrote: >> Clarify that ssl_cert_file and ssl_key_file are only read on startup -- >> implying that the params can be changed and the files moved to the new >> location/name without requiring a restart. Of course a restart is good to >> validate that the params and files are configured correctly. > The docs say that you can only change this in postgresql.conf or on the > command line. Changes to postgresql.conf requires pg_ctl reload or > something similar. The actual problem with this change request is that it's wrong. We've supported changing ssl_cert_file --- either the GUC value or the file contents --- via "pg_ctl reload" or equivalent for years now (cf. commits de41869b6, 6667d9a6d). So I don't see anything wrong with the docs text as it stands. regards, tom lane