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(-)