Re: Refactor SSL test framework to support multiple TLS libraries

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Refactor SSL test framework to support multiple TLS libraries
Дата
Msg-id YGL1LVGdzfUZY0tQ@paquier.xyz
обсуждение исходный текст
Ответ на Re: Refactor SSL test framework to support multiple TLS libraries  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Refactor SSL test framework to support multiple TLS libraries  (Andrew Dunstan <andrew@dunslane.net>)
Re: Refactor SSL test framework to support multiple TLS libraries  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: Refactor SSL test framework to support multiple TLS libraries  (Daniel Gustafsson <daniel@yesql.se>)
Список pgsql-hackers
On Tue, Mar 30, 2021 at 03:50:28PM +0900, Michael Paquier wrote:
> The test_*() ones are just wrappers for psql able to use a customized
> connection string.  It seems to me that it would make sense to move
> those two into PostgresNode::psql itself and extend it to be able to
> handle custom connection strings?

Looking at this part, I think that this is a win in terms of future
changes for SSLServer.pm as it would become a facility only in charge
of managing the backend's SSL configuration.  This has also the
advantage to make the error handling with psql more consistent with
the other tests.

So, attached is a patch to do this simplification.  The bulk of the
changes is within the tests themselves to adapt to the merge of
$common_connstr and $connstr for the new routines of PostgresNode.pm,
and I have done things this way to ease the patch lookup.  Thoughts?
--
Michael

Вложения

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

Предыдущее
От: Suraj Kharage
Дата:
Сообщение: extra semicolon in postgres_fdw test cases
Следующее
От: Markus Wanner
Дата:
Сообщение: Re: [PATCH] add concurrent_abort callback for output plugin