Ensure that STDERR is empty during connect_ok

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Ensure that STDERR is empty during connect_ok
Дата
Msg-id 9D4FFB61-392B-4A2C-B7E4-911797B4AC14@yesql.se
обсуждение исходный текст
Ответы Re: Ensure that STDERR is empty during connect_ok  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: Ensure that STDERR is empty during connect_ok  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Ensure that STDERR is empty during connect_ok  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
As part of the NSS patchset, quite a few bugs (and NSS quirks) were found by
inspecting STDERR in connect_ok and require it to be empty.  This is not really
NSS specific, and could help find issues in other libraries as well so I
propose to apply it regardless of the fate of the NSS patchset.

(The change in the SCRAM tests stems from this now making all testruns have the
same number of tests.  While I prefer to not plan at all and instead run
done_testing(), doing that consistently is for another patch, keeping this with
the remainder of the suites.)

--
Daniel Gustafsson        https://vmware.com/


Вложения

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

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: Deparsing rewritten query
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message