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
b) is their any known issues using "cross over using pg_upgrade " option between the server's having below said operating system
- 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"
On Tuesday, December 3, 2024 at 12:28:58 AM EST, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 12/2/24 17:23, Ron Johnson wrote: > Adrian, > > OP is moving to a new VM when migrating to PG 15. When was the > "cross-server" feature added to pg_upgrade? >
Moving to a new VM was not the issue, my mistake was thinking the OS version was staying the same.
Then:
On old VM:
"take offline full backup (PG_DATA folder alone) using OS command"
On new VM: "Restore offline full backup (PG_DATA folder alone) using OS command"
Followed by installing new Postgres version could be dealt with using pg_upgrade. Once I was corrected on what was actually going on then doing a dump/restore or logical replication became better choices.
