mirror of
https://github.com/postgres/postgres.git
synced 2025-07-12 21:01:52 +03:00
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.
This commit is contained in:
@ -512,7 +512,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
|
||||
@ -524,10 +524,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
|
||||
}
|
||||
|
Reference in New Issue
Block a user