From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Mathias Kunter <mathiaskunter@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster
Date: Wed, 29 Dec 2021 11:20:06 +0100
Message-ID: <608adaf4-7637-9a34-95d5-0ca948437f5d@enterprisedb.com> (raw)
In-Reply-To: <10f71bb9-2ca6-24c4-0feb-f64138a0e4b3@gmail.com>
References: <17347-27b988f51d9dee1a@postgresql.org>
<1760674.1640707235@sss.pgh.pa.us>
<10f71bb9-2ca6-24c4-0feb-f64138a0e4b3@gmail.com>
On 28.12.21 19:12, Mathias Kunter wrote:
>> It's a bit moot now anyway, since pg_upgrade doesn't create
>> that script anymore in v14 and up.
>
> The docs at https://www.postgresql.org/docs/14/pgupgrade.html (step 15
> "Statistics") though say the user must "run a command to regenerate that
> information". Is the documentation up-to-date?
It actually says "you will be instructed to run a command [...]", which
is what happens: It prints out a command that you can use. It also says
"You might need to set connection parameters to match your new
cluster.", which could apply to your situation.
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: peter.eisentraut@enterprisedb.com, mathiaskunter@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster
In-Reply-To: <608adaf4-7637-9a34-95d5-0ca948437f5d@enterprisedb.com>
* 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