pgsql: Improve reporting of pg_upgrade log files on test failure - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Improve reporting of pg_upgrade log files on test failure
Date
Msg-id E1tL9zC-0026sO-EA@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Improve reporting of pg_upgrade log files on test failure

On failure, the pg_upgrade log files are automatically appended to the
test log file, but the information reported was inconsistent.

A header, with the log file name, was reported with note(), while the
log contents and a footer used print(), making it harder to diagnose
failures when these are split into console output and test log file
because the pg_upgrade log file path in the header may not be included
in the test log file.

The output is now consolidated so as the header uses print() rather than
note().  An extra note() is added to inform that the contents of a
pg_upgrade log file are appended to the test log file.

The diffs from the regression test suite and dump files all use print()
to show their contents on failure.

Author: Joel Jacobson
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/49f7e64a-b9be-4a90-a9fe-210a7740405e@app.fastmail.com
Backpatch-through: 15

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8afff7d6db25ab52f155d8a220f692d7d6d84152

Modified Files
--------------
src/bin/pg_upgrade/t/002_pg_upgrade.pl | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Speedup Hash Joins with dedicated functions for ExprState hashin
Next
From: Jeff Davis
Date:
Subject: pgsql: Use in-place updates for pg_restore_relation_stats().