Re: [PATCH] Reload SSL certificates on SIGHUP
От | Michael Paquier |
---|---|
Тема | Re: [PATCH] Reload SSL certificates on SIGHUP |
Дата | |
Msg-id | CAB7nPqRFffNTnTo5indiY_5oRavF-XN1vN1JC9WZeUYW3ZYqaw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Reload SSL certificates on SIGHUP (Andreas Karlsson <andreas@proxel.se>) |
Ответы |
Re: [PATCH] Reload SSL certificates on SIGHUP
|
Список | pgsql-hackers |
On Wed, Nov 9, 2016 at 3:48 AM, Andreas Karlsson <andreas@proxel.se> wrote: > On 11/08/2016 01:22 PM, Michael Banck wrote: >> >> Thanks! I couldn't find furhter faults in my testing. I guess the >> question what to do about this on Windows is possibly still open, but as >> I am not familiar with the Windows port at all I've marked it Ready for >> Committer for now. > > Thanks again for the review! It seems to me that this patch is missing something... To begin with, src/test/ssl/ServerSetup.pm should be patched so as the new SSL configuration is reloaded after pg_ctl reload, and not after an instance restart. That's straight-forward: --- a/src/test/ssl/ServerSetup.pm +++ b/src/test/ssl/ServerSetup.pm @@ -96,7 +96,7 @@ sub configure_test_server_for_ssl close HBA; } -# Change the configuration to use given server cert file, and restart +# Change the configuration to use given server cert file, and reload # the server so that the configuration takes effect. sub switch_server_cert { @@ -115,6 +115,6 @@ sub switch_server_cert print SSLCONF "ssl_crl_file='root+client.crl'\n"; close SSLCONF; - # Stop and restart server to reload the new config. - $node->restart; + # Reload the new configuration set. + $node->reload; } Once I did that, half of the tests are failing. And I would have expected all of them to work properly. -- Michael
Вложения
В списке pgsql-hackers по дате отправления: