pgsql: Move any remaining files generated by pg_upgrade into an interna - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Move any remaining files generated by pg_upgrade into an interna
Date
Msg-id E1oXuu7-0005bW-5v@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Move any remaining files generated by pg_upgrade into an internal subdir

This change concerns a couple of .txt files (for internal state checks)
that were still written in the path where the binary is executed, and
not in the subdirectory located in the target cluster.  Like the other
.txt files doing already so (like loadable_libraries.txt), these are
saved in the base output directory.  Note that on failure, the logs
report the full path to the .txt file generated, so these are easy to
find.

Oversight in 38bfae3.

Author: Daniel Gustafsson
Reviewed-by: Michael Paquier, Justin Prysby
Discussion: https://postgr.es/m/181A6DA8-3B7F-4B71-82D5-363FF0146820@yesql.se
Backpatch-through: 15

Branch
------
REL_15_STABLE

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

Modified Files
--------------
src/bin/pg_upgrade/check.c   | 12 +++++++++---
src/bin/pg_upgrade/version.c | 12 +++++++++---
2 files changed, 18 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Don't reference out-of-bounds array elements in brin_minmax_mult
Next
From: Michael Paquier
Date:
Subject: pgsql: Rename macro related to pg_backup_stop()