| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Mathias Kunter <mathiaskunter(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster |
| Date: | 2021-12-29 10:20:06 |
| Message-ID: | 608adaf4-7637-9a34-95d5-0ca948437f5d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mr. Keaton | 2021-12-29 15:01:29 | Re: BUG #17348: Can never install pgsql on Ubuntu |
| Previous Message | Andreas Dijkman | 2021-12-28 20:36:22 | Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core |