From: Michael Paquier <michael@paquier.xyz>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix thinko with subdirectories generated by pg_upgrade for inter
Date: Tue, 15 Feb 2022 02:47:41 +0000
Message-ID: <E1nJnsT-0002aj-Q9@gemulon.postgresql.org> (raw)
Fix thinko with subdirectories generated by pg_upgrade for internal files
38bfae3 has mixed the "dump/" and "log/" subdirectories generated in
"pg_upgrade_output.d/", causing the internal dump files to be generated
in "log/" and the log files to be in "dump/", but the opposite should be
done. This was not directly an issue for pg_upgrade runs, as the
internal dump files were still picked up at the location of their
creation, but the newest version of the buildfarm client would have
reported the dump files instead of the log files on failures of
pg_upgrade.
Issue spotted while testing the TAP tests of pg_upgrade.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a008496300110d1b5ab7cb29b67ac043a6999bdb
Modified Files
--------------
src/bin/pg_upgrade/pg_upgrade.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz
Subject: Re: pgsql: Fix thinko with subdirectories generated by pg_upgrade for inter
In-Reply-To: <E1nJnsT-0002aj-Q9@gemulon.postgresql.org>
References: <E1nJnsT-0002aj-Q9@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox