Feedback-ID: i76984098:Fastmail
Message-ID: <a779ef21-f04d-4a51-83d3-51632b0fb3fa@aklaver.com>
Date: Wed, 4 Dec 2024 09:04:26 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
 ver 15.X
To: Bharani SV-forum <esteembsv-forum@yahoo.com>,
 Ron Johnson <ronljohnsonjr@gmail.com>,
 pgsql-general <pgsql-general@postgresql.org>
References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com>
 <A01D7215-2691-4FA6-8B79-E197B7DB9351@gmail.com>
 <98965993.3138805.1731699978332@mail.yahoo.com>
 <564950518.5117550.1733177884387@mail.yahoo.com>
 <CANzqJaAda4nZbkG=c+72ry5GdaxrJ6Jzr6fz1quhq8tTfaX1Pg@mail.gmail.com>
 <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com>
 <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com>
 <CANzqJaC1Uk4H=55vV_jbFYMuD1f9Bb_4Y9WKvkZA3bt92bEUnw@mail.gmail.com>
 <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com>
 <1061066336.5835157.1733316137292@mail.yahoo.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <1061066336.5835157.1733316137292@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/a779ef21-f04d-4a51-83d3-51632b0fb3fa%40aklaver.com>
Precedence: bulk

On 12/4/24 04:42, Bharani SV-forum 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"

That will not work as you would need an install of Postgres 13 on the 
new machine as well. And then there is the issue that the OS version 
changed as well. That would cause issues. Follow the process Greg Sabino 
Mullane posted.

> 
> 
> 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.
> 
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com