From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: mathiaskunter@gmail.com
Subject: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster
Date: Tue, 28 Dec 2021 09:47:42 +0000
Message-ID: <17347-27b988f51d9dee1a@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17347
Logged by: Mathias Kunter
Email address: mathiaskunter@gmail.com
PostgreSQL version: 12.9
Operating system: Debian 10.11
Description:
When upgrading a PostgreSQL cluster with pg_upgrade (tested while upgrading
from 11.14 to 12.9, but supposedly affects all versions), and the --new-port
argument is used to specify a new port number for the upgraded cluster, then
the generated analyze_new_cluster script will connect to and analyze a
different cluster instead of the upgraded one.
The vacuumdb command found within the analyze_new_cluster script should
explicitly specify the port number of the upgraded cluster, so that it will
actually analyze the correct cluster after the upgrade.
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, mathiaskunter@gmail.com
Subject: Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster
In-Reply-To: <17347-27b988f51d9dee1a@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