pgsql: Use command_ok for pg_regress calls in 002_pg_upgrade and 027_st - Mailing list pgsql-committers

From Andrew Dunstan
Subject pgsql: Use command_ok for pg_regress calls in 002_pg_upgrade and 027_st
Date
Msg-id E1w8H7D-002bgb-09@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Use command_ok for pg_regress calls in 002_pg_upgrade and 027_stream_regress

Now that command_ok() captures and displays failure output, use it
instead of system() plus manual diff-dumping in these two tests.  This
simplifies both scripts and produces consistent, truncated output on
failure.

Author: Jelte Fennema-Nio <postgres@jeltef.nl>
Reviewed-by: Andrew Dunstan <andrew@dunslane.net>
Reviewed-by: Corey Huinker <corey.huinker@gmail.com>
Discussion: https://postgr.es/m/DFYFWM053WHS.10K8ZPJ605UFK@jeltef.nl

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/bb6ae9707c1789c9d2036c9bbd35965a01e1b214

Modified Files
--------------
src/bin/pg_upgrade/t/002_pg_upgrade.pl    | 40 ++++++++--------------
src/test/recovery/t/027_stream_regress.pl | 55 +++++++++----------------------
2 files changed, 29 insertions(+), 66 deletions(-)


pgsql-committers by date:

Previous
From: Tomas Vondra
Date:
Subject: pgsql: jit: Change the default to off.
Next
From: John Naylor
Date:
Subject: pgsql: Check for __cpuidex and __get_cpuid_count separately