pgsql: Avoid assuming that we know the spelling of getopt_long'serror

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Avoid assuming that we know the spelling of getopt_long'serror
Дата
Msg-id E1gkI4V-0001Db-8t@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Avoid assuming that we know the spelling of getopt_long's error messages.

I've had enough of "fixing" this test case.  Whatever value it has
is limited to verifying that pgbench fails for an unrecognized switch,
and we don't need to assume anything about what getopt_long prints in
order to do that.

Discussion: https://postgr.es/m/9427.1547701450@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/251f57460f123f28089ff23a7e43990618dd05a8

Modified Files
--------------
src/bin/pgbench/t/002_pgbench_no_server.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: pgsql: Restrict the use of temporary namespace in two-phasetransaction
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pgsql: Restrict the use of temporary namespace in two-phasetransaction