Commit 1a721248 authored by Andrew Dunstan's avatar Andrew Dunstan

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.
parent fd7d387e
...@@ -512,7 +512,7 @@ pgbench( ...@@ -512,7 +512,7 @@ pgbench(
qr{processed: 1/1}, qr{processed: 1/1},
qr{shell-echo-output} qr{shell-echo-output}
], ],
[qr{command=8.: int 2\b}], [qr{command=8.: int 1\b}],
'pgbench backslash commands', 'pgbench backslash commands',
{ {
'001_pgbench_backslash_commands' => q{-- run set '001_pgbench_backslash_commands' => q{-- run set
...@@ -524,10 +524,10 @@ pgbench( ...@@ -524,10 +524,10 @@ pgbench(
\sleep 0 s \sleep 0 s
\sleep :zero \sleep :zero
-- setshell and continuation -- setshell and continuation
\setshell two\ \setshell another_one\
expr \ echo \
1 + :one :one
\set n debug(:two) \set n debug(:another_one)
-- shell -- shell
\shell echo shell-echo-output \shell echo shell-echo-output
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment