| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Reload SSL certificates on SIGHUP |
| Date: | 2017-01-04 15:46:28 |
| Message-ID: | cf2ea102-13cd-d51a-8dfe-dfe6b9269e63@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/4/17 10:26 AM, Tom Lane wrote:
> Andreas Karlsson <andreas(at)proxel(dot)se> writes:
>> Sorry, I was very unclear. I meant refusing the reload the SSL context
>> if there is a pass phrase, but that the rest of the config will be
>> reloaded just fine. This will lead to some log spam on every SIGHUP for
>> people with a pass phrase but should otherwise work as before.
>
> How will you know whether there's a pass phrase?
One could register a password callback that remembers whether it was called.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2017-01-04 15:49:23 | Re: merging some features from plpgsql2 project |
| Previous Message | Merlin Moncure | 2017-01-04 15:36:25 | Re: emergency outage requiring database restart |