From: Andrew Dunstan Date: Wed, 24 Jul 2019 15:41:39 +0000 (-0400) Subject: Don't assume expr is available in pgbench tests X-Git-Tag: REL_12_BETA3~43 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bfa4263e7119685cddb08ed2e2b3462157d4d453;p=thirdparty%2Fpostgresql.git Don't assume expr is available in pgbench tests Windows hosts do not normally come with expr, so instead of using that to test the \setshell command, use echo instead, which is fairly universally available. Backpatch to release 11, where this came in. Problem found by me, patch by Fabien Coelho. --- diff --git a/src/bin/pgbench/t/001_pgbench_with_server.pl b/src/bin/pgbench/t/001_pgbench_with_server.pl index 3b097a91b28..85ad5ac14b8 100644 --- a/src/bin/pgbench/t/001_pgbench_with_server.pl +++ b/src/bin/pgbench/t/001_pgbench_with_server.pl @@ -510,7 +510,7 @@ pgbench( qr{processed: 1/1}, qr{shell-echo-output} ], - [qr{command=8.: int 2\b}], + [qr{command=8.: int 1\b}], 'pgbench backslash commands', { '001_pgbench_backslash_commands' => q{-- run set @@ -522,10 +522,10 @@ pgbench( \sleep 0 s \sleep :zero -- setshell and continuation -\setshell two\ - expr \ - 1 + :one -\set n debug(:two) +\setshell another_one\ + echo \ + :one +\set n debug(:another_one) -- shell \shell echo shell-echo-output }