Patch: Don't set LoadedSSL unless secure_initialize succeeds

Поиск
Список
Период
Сортировка
От Gurjeet Singh
Тема Patch: Don't set LoadedSSL unless secure_initialize succeeds
Дата
Msg-id CABwTF4VOUXC7bpfCzAmTpbsE71FiNnu=FFRB1CRzL1AviD=qWg@mail.gmail.com
обсуждение исходный текст
Ответы Re: Patch: Don't set LoadedSSL unless secure_initialize succeeds  (Daniel Gustafsson <daniel@yesql.se>)
Список pgsql-hackers
Дерево обсуждения 
The initialization in PostmasterMain() blindly turns on LoadedSSL,
irrespective of the outcome of secure_initialize(). I don't think
that's how it should behave, primarily because of the pattern followed
by the other places that call secure_initialize().

This patch makes PostmasterMain() behave identical to other places
(SIGHUP handler, and SubPostmasterMain()) where LoadedSSL is turned on
after checking success of secure_initialize() call. Upon failure of
secure_initialize(), it now emits a log message, instead of setting
LoadedSSL to true.

Best regards,
Gurjeet
http://Gurje.et
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Noah Misch
Дата:
Сообщение: Re: tweak to a few index tests to hits ambuildempty() routine.
Следующее
От: Daniel Gustafsson
Дата:
Сообщение: Re: Patch: Don't set LoadedSSL unless secure_initialize succeeds