Re: [HACKERS] [PATCH] Reload SSL certificates on SIGHUP
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] [PATCH] Reload SSL certificates on SIGHUP |
Дата | |
Msg-id | 16e282a4-2573-f629-09e8-e6b0ac615890@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Reload SSL certificates on SIGHUP (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] [PATCH] Reload SSL certificates on SIGHUP
|
Список | pgsql-hackers |
On 12/5/16 12:17 AM, Michael Paquier wrote: > OK, here is attached what I had in mind as reload-ssl-v08-02.patch for > reference. This applies on top of the main patch > reload-ssl-v08-01.patch that is the same version as v7 with the issues > I reported previously as addressed. LoadedSSL is mapped with a > read-only GUC parameter that new sessions can query after connecting. > The only use case where that would be useful would be when using > sslmode=prefer to check whether the SSL context is loaded even if ssl > has been switched from off to on. But let's be honest, pg_stat_ssl > reports already this kind of information, making this patch at the end > useless because LoadedSSL does not change for an already-spawned > backend. Yeah, it seems that if you want to know whether you are using SSL, then we already have that. I don't see the need for this new read-only setting. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: