Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X

On Wed, Dec 4, 2024 at 7:42 AM Bharani SV-forum <esteembsv-forum(at)yahoo(dot)com>
wrote:

> Team /Ron/Adrian
>
> Wann to reconfirm
> we have an setup with
>
> new server will be with
>
> will be following the following suggestion
>
> *On old VM* [ existing server with OS "Amazon Linux release 2 (Karoo) "
> present in aws "us-east-1 region" and along with postgresql ver 13.16.2 -
> community edn ]
>
> - "take offline full backup (PG_DATA folder alone) using OS command"
>
> *On new VM [OS "Amazon Linux 2023 " in aws region=us-east-1 and intended
> db as "postgresql 15.10 - community edn" ] *
>
> - "Restore offline full backup (PG_DATA folder alone) using OS command"
> - create postgres unix userid
> - install postgresql ver 15.10 binaries
> - setup respective env variable to point correctly for PG_DATA
> - will follow "pg_upgrade"
>
>
> my question is
> a) is the above said steps is correct with the given existing and proposed
> setup
>

No. You're vastly overcomplicating things.

> b) is their any known issues using "cross over using pg_upgrade " option
> between the server's having below said operating system
>

There is no "cross over using pg_upgrade" because it does not exist.

When migrating from OldServer to NewServer, your options are:
A) pg_dump/pg_restore
B) Logical Replication

> *- source = existing server with OS = *Amazon Linux release 2 (Karoo) "
> present in aws "us-east-1 region" and along with postgresql ver 13.16.2 -
> community edn
> vs
> target - different server *OS "Amazon Linux 2023 " in aws
> region=us-east-1 and intended db as "postgresql 15.10 - community edn"*
>

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!