| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | mathiaskunter(at)gmail(dot)com |
| Subject: | BUG #17347: pg_upgrade: analyze_new_cluster script analyzes wrong cluster |
| Date: | 2021-12-28 09:47:42 |
| Message-ID: | 17347-27b988f51d9dee1a@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17347
Logged by: Mathias Kunter
Email address: mathiaskunter(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2021-12-28 13:14:03 | Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance |
| Previous Message | Daniel Gustafsson | 2021-12-27 23:26:17 | Re: BUG #17346: pg_upgrade fails with role granted by other role |