Thanks, let me try that out.
But is there a way to know for sure if pg_upgrade will have any such problems?
Other than FDW's owner, any other things I should check before upgrading other clusters?
Regards
Abhishek Bhola
On Fri, 2021-10-22 at 17:11 +0900, Abhishek Bhola wrote:
> postgres@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