| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | colinthart(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Which parameters are only used on startup? |
| Date: | 2025-12-23 00:29:10 |
| Message-ID: | 651983.1766449750@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-12-23 00:42:12 | Re: change ON CONFLICT UPDATE |
| Previous Message | Bruce Momjian | 2025-12-23 00:14:31 | Re: Which parameters are only used on startup? |