| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Geoghegan <pg(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Reload SSL certificates on SIGHUP |
| Date: | 2016-12-04 14:11:24 |
| Message-ID: | 6d45be21-637b-c802-75e7-1ea634ed4089@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/04/2016 02:12 PM, Michael Paquier wrote:
> One last thing that I think is missing in this patch is for users the
> possibility to check via SQL if the SSL context is actually loaded or
> not. As the context is reloaded after all the new values are
> available, with the current patch users may see that ssl is set to on
> but no context is loaded. So why not adding for example a read-only
> parameter that maps with SSLLoaded?
The other three issues are easy to fix, but this one is a bit trickier.
Do you mean that we should add another GUC here which is read-only? Does
this have a precedent in the code?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-12-04 14:20:05 | Re: [PATCH] Reload SSL certificates on SIGHUP |
| Previous Message | Julien Rouhaud | 2016-12-04 13:29:17 | Re: Rename max_parallel_degree? |