It may say “in the new cluster” but it was not clear to me if that was “in the
new cluster (before the upgrade starts)” or “in the new cluster (after the
upgrade completes)”
In hind sight everything makes sense, but in the present it was very confusing.
-Charlie
> On Jan 26, 2021, at 2:39 AM,
On Tue, Jan 26, 2021 at 10:27:23AM +0100, Daniel Gustafsson wrote:
> > On 26 Jan 2021, at 09:39, Laurenz Albe wrote:
>
> > But perhaps it would not harm to be more explicit and add something like
> > that:
> >
> > "Do not create and users, tablespaces or other objects on the new cluster."
>
> +
> On 26 Jan 2021, at 09:39, Laurenz Albe wrote:
> But perhaps it would not harm to be more explicit and add something like
> that:
>
> "Do not create and users, tablespaces or other objects on the new cluster."
+1, that makes sense (with a s/and/any/).
--
Daniel Gustafsson https:
On Tue, 2021-01-26 at 06:57 +, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/13/pgupgrade.html
> Description:
>
> During the pg_upgrade process, a check is run to make sure
> pg_catalog.pg_roles has only a single non pg_* user, typically this is just
> 'postgres'. If this
I see now that the user check was verifying the target database and not the
source. My upgrade script (which I used from 11 to 12) initialized the target
database for upgrades as it did for seeding from scratch which included a user
account. I removed that part of the script and the upgrade comp
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/pgupgrade.html
Description:
During the pg_upgrade process, a check is run to make sure
pg_catalog.pg_roles has only a single non pg_* user, typically this is just
'postgres'. If this check
