From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Abhishek Bhola <abhishek(dot)bhola(at)japannext(dot)co(dot)jp>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [Major version upgrade] pg_upgrade fails despite passing check mode |
Date: | 2021-10-22 15:20:55 |
Message-ID: | 13e858eeec8fc0e0e67090c5abc14530114d03a3.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2021-10-22 at 17:11 +0900, Abhishek Bhola wrote:
> postgres(at)dxxxpgs03:/Dxxxx1/datadg/data13$ /usr/pgsql-13/bin/pg_upgrade -k --check
> --new-datadir='/Dxxxx1/datadg/data13' --old-datadir='/Dxxxx1/datadg/data'
> --new-bindir='/usr/pgsql-13/bin' --old-bindir='/usr/pgsql-11/bin'
>
> *Clusters are compatible*
>
> But then while performing the actual upgrade, it failed saying the "owner of a FDW should be a super user"
>
> So I started the old Postgres 11 again, changed the owner of that FDW to a super user.
>
> Now when I try to run the upgrade (even in check mode) again, it says "new cluster tablespace directory already exists"
>
> Is it safe to delete the new tablespace directories?
Don't remove the tablespace directories, because they contain the original data from the
old cluster. But there should be directories called PG_13_202007201, and you have to
remove those.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ninad Shah | 2021-10-22 15:40:31 | Issue with pg_basebackup v.11 |
Previous Message | Ninad Shah | 2021-10-22 15:12:32 | Re: spannerdb migration to PostgreSQL |