| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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:26:19 |
| Message-ID: | 22644.1483543579@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-01-04 15:33:27 | Re: increasing the default WAL segment size |
| Previous Message | Peter Eisentraut | 2017-01-04 15:21:21 | Re: [PROPOSAL] Temporal query processing with range types |