Message-ID: <608adaf4-7637-9a34-95d5-0ca948437f5d@enterprisedb.com>
Date: Wed, 29 Dec 2021 11:20:06 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.4.0
Subject: Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong
 cluster
Content-Language: en-US
To: Mathias Kunter <mathiaskunter@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
References: <17347-27b988f51d9dee1a@postgresql.org>
 <1760674.1640707235@sss.pgh.pa.us>
 <10f71bb9-2ca6-24c4-0feb-f64138a0e4b3@gmail.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <10f71bb9-2ca6-24c4-0feb-f64138a0e4b3@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/608adaf4-7637-9a34-95d5-0ca948437f5d%40enterprisedb.com>
Precedence: bulk

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.