public inbox for [email protected]help / color / mirror / Atom feed
Which parameters are only used on startup? 4+ messages / 3 participants [nested] [flat]
* Which parameters are only used on startup? @ 2025-11-26 09:34 PG Doc comments form <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: PG Doc comments form @ 2025-11-26 09:34 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/runtime-config-connection.html Description: 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. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Which parameters are only used on startup? @ 2025-12-23 00:14 Bruce Momjian <[email protected]> parent: PG Doc comments form <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Bruce Momjian @ 2025-12-23 00:14 UTC (permalink / raw) To: [email protected]; [email protected] On Wed, Nov 26, 2025 at 09:34:18AM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/18/runtime-config-connection.html > Description: > > 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. I am not aware of anyone else who thinks changing postgresql.conf and then reloading causes the session to use new ssl keys/files, and explaining that in the docs might be more confusing than helpful. -- Bruce Momjian <[email protected]> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Which parameters are only used on startup? @ 2025-12-23 00:29 Tom Lane <[email protected]> parent: Bruce Momjian <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Tom Lane @ 2025-12-23 00:29 UTC (permalink / raw) To: Bruce Momjian <[email protected]>; +Cc: [email protected]; [email protected] Bruce Momjian <[email protected]> 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 ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Which parameters are only used on startup? @ 2025-12-23 00:50 Bruce Momjian <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Bruce Momjian @ 2025-12-23 00:50 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected]; [email protected] On Mon, Dec 22, 2025 at 07:29:10PM -0500, Tom Lane wrote: > Bruce Momjian <[email protected]> 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. I had trouble parsing his text too but I think the original poster's point was that changing these values don't affect a connected session. When the original poster says restart, I think he/she means restart the session, not the postmaster, but I am not 100% clear on that either. -- Bruce Momjian <[email protected]> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future. ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-12-23 00:50 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-11-26 09:34 Which parameters are only used on startup? PG Doc comments form <[email protected]> 2025-12-23 00:14 ` Bruce Momjian <[email protected]> 2025-12-23 00:29 ` Tom Lane <[email protected]> 2025-12-23 00:50 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox