Move any remaining files generated by pg_upgrade into an internal subdir
authorMichael Paquier <michael@paquier.xyz>
Tue, 13 Sep 2022 01:38:56 +0000 (10:38 +0900)
committerMichael Paquier <michael@paquier.xyz>
Tue, 13 Sep 2022 01:38:56 +0000 (10:38 +0900)
commitee5353abb6124de5ffd24ef1cedbc2a7196d4fd5
treeda6ed57d98ec4c8688654a0ad14d0521f059d240
parent6b89ce1a21f909f616db165dcc6d8d2918fbc185
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
src/bin/pg_upgrade/check.c
src/bin/pg_upgrade/version.c