From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench tests vs Windows |
Date: | 2019-07-23 23:13:51 |
Message-ID: | 2223.1563923631@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> In commit ed8a7c6fcf9 we added some extra tests to pgbench, including
> this snippet:
> \setshell two\
> expr \
> 1 + :one
> Unfortunately, this isn't portable, as I've just discovered at the cost
> of quite a bit of time. In particular, you can't assume expr is present
> and in the path on Windows.
Ugh.
> The Windows equivalent would be something like:
> \setshell two\
> @set /a c = 1 + :one && echo %c%
I wonder how universal that is, either.
> I propose to prepare a patch along these lines. Alternatively we could
> just drop it - I don't think the test matters all that hugely.
I'd say try that, but if it doesn't work right away, just skip the
test on Windows.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-07-23 23:29:04 | Re: stress test for parallel workers |
Previous Message | Justin Pryzby | 2019-07-23 23:04:40 | Re: stress test for parallel workers |