| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Dávid Suchan <david(dot)suchan(at)student(dot)tuke(dot)sk> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade Only the install user can be defined in the new cluster |
| Date: | 2023-03-16 19:14:43 |
| Message-ID: | CFECA208-47CA-40C3-B022-4CDCFD4D03EC@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 16 Mar 2023, at 15:56, Dávid Suchan <david(dot)suchan(at)student(dot)tuke(dot)sk> wrote:
>
> So I tried upgrading into this brand new cluster I created(using initdb -D /somedatapathichose). Running the upgrade with --check worked, it returned message that the clusters are identical. Then I stopped the new cluster, and ran the pg_upgrade without --check, which resulted in another:
> Checking database user is the install user
pg_upgrade --check does not alter the new cluster in any way, so you must have
some form of processing on your system that configured the new cluster with
roles (and possibly other things) in between these runs.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-03-16 19:24:49 | Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows! |
| Previous Message | Tom Lane | 2023-03-16 18:24:28 | Re: pg_upgrade Only the install user can be defined in the new cluster |