Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLS8n-00EsYo-AS for pgsql-general@arkaria.postgresql.org; Wed, 11 Dec 2024 19:12:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tLS8k-001Jxj-P2 for pgsql-general@arkaria.postgresql.org; Wed, 11 Dec 2024 19:12:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLS8k-001JxZ-A6 for pgsql-general@lists.postgresql.org; Wed, 11 Dec 2024 19:12:55 +0000 Received: from sonic316-11.consmr.mail.bf2.yahoo.com ([74.6.130.121]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tLS8i-002K5K-6i for pgsql-general@postgresql.org; Wed, 11 Dec 2024 19:12:54 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733944369; bh=gwz2u4q3CH+Z/SB1VYUV8IQM+S3F/bOr2M/aRPFitvQ=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=f4dSo/68xPbFhwJ/CuYsIMQx+SwEAlE+XmUOmT6VoyJgvN9oaqqGR3nBKS8ScVPwbgF8fX1B6+jh0u4FiEhqg/UHPfEgLIi+B5jgW7B8fhFvVGYQnAOT/hQ3U4y7Hn7Tydgg4eKszn7TMbyoH9saZ64FgWx3hSGc2kKaryO0iQuB1e+yfp2j9tYr83QtcZsqTmahu11tQjBwUG94I95FUB5ZcC3bJw/quxAlU6bhXiI9t0Jnx6MXOpotbdxsMwb6o7GWvrXpF6OJ9jUWoC0f/6TsPn3DvjXeJVnrUhsGnl3ONwq2hKwkaLew8ZkOFsd/qE2iTsykFnZBb7ke4j8U/Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733944369; bh=kwYam4rq0s3bV0OMa7P4eoG1wqSwOyMXoAkzmE5f6xb=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=gYSun0h/yVj5h/PmmktkL0TnKf14j+u27pFIYluxR0AeQllMGlyb2YVFDQG9AqB2neTSf3YAe1J8qQ52DlSFdpY4ctjq8eTh/VI61zoWnT3ZgIXn82323qZPppYu4nMO60SI6RctbWLiCg3B1uamdj4DddNhFi7zXBQjOnf0yjEVP9wcuQ+rmYazASMMfz3IUtAVeYgP8ORnop9bEi0WIClfmERlF/nZ5zU2SGSZ3K/5Lr6W4N8BSNmjV+ETxqbVFBqZy4L9RgfhMl8gJ7uV+P1NBOQPg6UjArNNvhmB4ELFq3DKPX0rURCbGvq1ilc/b/7wJagNdnQljMY+pWIypA== X-YMail-OSG: 7FOtOTMVM1nIHj13CtU5IGCnhcBT8JsHAhS8oI7EMNxyrvKN8EEvvBjaROBiFoZ qWKejn6C_TizsRN2QwC2TJmDFB7Hq_pSYKwPoskf_lXnI4fAfVOW594MWIHHAvjZyFCkmLFa0zCY OrEdC6uj4DIK688L8vrWI95MUZAfyoojjycCjpnnrtwmNhggYXQtzLfoARUGJX4Cvuq.57zoD5a3 XWjC8kg.GOzs6XCEtISvPcQ2D7FTw6IBTzKa0NBSR.H2FpYYZnP_a.q.v5Q19KEuwpiJIALuNiOn TIFi0YSvO6nqHAqbBIYdjH54YTmSM6n4RDs2irtKsCI0_Zo58LosDeZhxFtFqt5G0X3vgpsB70ED GZFgd0J.um4FFjtfmgOb927iOGmw3EgSn9oO6v.cqG.4sjEXTkWVocQfbBg_KABtvATw1LCkUx4Q jPatR7N2wYGH666sAs.6lpSV.fGPJesDayRjuWyr76ItBpiShRoAipyfiwqWONtKjsWxEMIV_Uiw _3OjZB1vLwPmfK1ODH0cdJgdKo0fBgUY9sZuvxEqd85ME2YcQs00VyE7sGTzADUg.QB.QeTXhF4m LkUjfoGKLq3olNCx.WZJjj927HymjmpjNBfY8LLpIguaDFmLAVDP853Iy4UtUHS9gbhLHoUyDo7r sDtAmPpgf0u5pw0fB6psg.58S8KnaaAz1b72gQIxG5kW9Sr_LSQgeAgRE9cwT6cmYGYP_C4CrVmj fEAWtJxbv5429RWH7uHgF7GeDcpYmZyPHRYNjaG4gPRwnqVqcj6R1js7Bk8IxOd410AvXm1L1gUa 3UMN_LhjSxqQx8oU430d6jg5Jpd1W0EZzGEey20GMspLNOlS80MY3mDqTZzKhZXhUyOhjGCRthJh h2gkB43a0Iyt3n9w9eDsUFW_YLlXz3DypZQd_etATHrY2ki3kFzcqdzDPZ3Md_f32TPpDewRCmhs nn7YWzRsoYAiqTp9Zg4AdNcuYLkXKSlfpyQtNPletGO43jAj.qiBia8b_UFDOmZr2ND7ib85zrJs U9leoKRe7ExnW8i6O9G7Qs.BCXQdKyd7ID_8JlD85bePDTbtkn6zX5YMvmxVHxsdaYBdvEjyVo6k 9z2qdGhSsptX3XpjuY8FyWwNtOzq8G0ZbiJPzQBycXuSuZ7EPsx9.4IXaYZipbNvXBH8A6iJtTPV _XEBcNTwugQCqo4Vfds0ygV37C9.4JoH.T0k_IFkBvGvBbfFgOIVdD8wWtQiJy.P4X_fhjJ3pvSv eoGF1xvHOXTqNWKL6JkoCmKPajSZHKm.XpCNK81VFivh1zAzHqcPF6lpjfKKLbyRkj2SuYGRYUnc sMtmcA2PkEK2GsJqG1A32TqX_BqA.nEt0rLFqidKhuJtx2sVFZc2gB0hM0qbd_PO5K9INFLckXax phpEdoyfQUQqjgyCopwL9Zisvl4ClmOHm3kwS9ZysHM13uUPJLg5SM2G1tbR7qi1Im7YJ7xBY72o .TuJ.fNViDA4SWz3RYR4I7K268p_obHYCtAVHVebfWaTnYAZg.pv_D9Lr._uixeay7gWdGxf20dm PL3xVOcLFTSE4spjXnWdg1LezK16HJkoy0xCQ8YUMYBjGtXl4IXHj4XYKxjKb.XVeS0.cqHtiZqu kIXeNyrqAiE3bskTIcX1RLCBVcF0k1QXbf6cqQYfNhzPtzvH8r3o_5lT7znQcvbUpjyn9zOb6ky9 f8nNYHoYMbxT7mWAYQnH8bvfZgnk6voezQWegkYCGbTohjUZnH5euVLY09uwoTs9ZBcSFv3fN_OB UuiI6Qfyuqkh9IPe5CDbDye6K0DybcGKdGAfMVk3BniphagIpisnIZ_qAHu2mrud.oF3ov2wyPwG 867LXqh858.SjWnIm4Jc33yKywgp0i8OhLDfpOMi06Wy7bsivdKKO2CBW0FHY9TeLveqeKnzufMX eGpFBE6C9PFgfwMEcLs6_6nX7TbqL8GH5iNO15fncfcyUvtvd0FUplvqCzm5eu1U20MH_jpUTksO Dv_GKFgjyW3QDUHj2drG7g6L01tMfqjZRyQ5d7qSX.hIK0OBQaKFgledpvwuEDqdIL8xwDVyvveH 5thCnM3ltoSy67nYNOuUIwFaaRZKjFqzhewNkx6e5eJE2MU1BfypEeDO9b6S__NjuEX7IC8rdLTQ 0MaT3QpJOrxFKj02n5hQn9Fg7PK8GbeXYQG_mqLJSDt1QmYMTzI_kxnQvq7u5K1JVD0pfsKtJsMD 7AESm0ztHMA18qOTYa0Cv33eG6UME4eg6uIg5XbNqbJIBoJWcm1hyXeLWytBkkFdrsTnqy4mBUh6 fkheX9UNwU0fC X-Sonic-MF: X-Sonic-ID: 273aba2a-fc83-4839-a56e-74287d3191e8 Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Wed, 11 Dec 2024 19:12:49 +0000 Date: Wed, 11 Dec 2024 19:12:44 +0000 (UTC) From: Bharani SV-forum To: Ron Johnson , pgsql-general , Adrian Klaver Message-ID: <1918413683.2239751.1733944364448@mail.yahoo.com> In-Reply-To: References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> Subject: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2239750_223327809.1733944364447" X-Mailer: WebService/1.1.23040 YMailNorrin Content-Length: 11085 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_2239750_223327809.1733944364447 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable TeamAs suggested from old server, post shutdown of DB, I did OS level dump= of PG_DATA folder and had restored in the new server. Any idea on how to install the older binary postgres 13.18 ( OS=3DAmazon Li= nux 2023.6.20241121) under a dedicated folder suffixed as the following e.g= .) /usr/pgsql1318 System Admin had already installed newer version pgsql 15.08 binaries in th= e=C2=A0 new server (OS=3D Amazon Linux 2023.6.20241121) in the folder "/usr= /bin/" We were quoted , OS =3D Amazon Linux 2023.6.20241121 doesnot support postgr= es ver 15.10 (Community edition) under its AWS-EC2. Regards On Wednesday, December 4, 2024 at 12:04:47 PM EST, Adrian Klaver wrote: =20 =20 On 12/4/24 04:42, Bharani SV-forum wrote: > Team /Ron/Adrian >=20 > Wann to reconfirm > we have an setup with >=20 > new server will be with >=20 > will be following the following suggestion >=20 > *On old VM* [ existing server with OS "Amazon Linux release 2 (Karoo) "= =20 > present in aws "us-east-1 region" and along with postgresql ver 13.16.2= =C2=A0=20 > - community edn ] >=20 >=C2=A0 =C2=A0- "take offline full backup (PG_DATA folder alone)=C2=A0 usin= g OS command" >=20 > *On new VM [OS "Amazon Linux 2023 " in aws region=3Dus-east-1 and intende= d=20 > db as "postgresql 15.10 - community edn" ] * >=20 >=C2=A0 =C2=A0- "Restore offline full backup (PG_DATA folder alone) using O= S 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=20 new machine as well. And then there is the issue that the OS version=20 changed as well. That would cause issues. Follow the process Greg Sabino=20 Mullane posted. >=20 >=20 > my question is > a) is the above said steps is correct with the given existing and=20 > proposed setup > b) is their any known issues using "cross over using pg_upgrade " option= =20 > between the server's having below said operating system > *- source =3D existing server with OS =3D *Amazon Linux release 2 (Karoo)= "=20 > present in aws "us-east-1 region" and along with postgresql ver 13.16.2= =C2=A0=20 > - community edn > vs > target - different server *OS "Amazon Linux 2023 " in aws=20 > region=3Dus-east-1 and intended db as "postgresql 15.10 - community edn"* > * > * > * > * > On Tuesday, December 3, 2024 at 12:28:58 AM EST, Adrian Klaver=20 > wrote: >=20 >=20 > On 12/2/24 17:23, Ron Johnson wrote: >=C2=A0 > Adrian, >=C2=A0 > >=C2=A0 > OP is moving to a new VM when=C2=A0migrating to PG 15.=C2=A0 When= was the >=C2=A0 > "cross-server" feature added to pg_upgrade? >=C2=A0 > >=20 > Moving to a new VM was not the issue, my mistake was thinking the OS > version was staying the same. >=20 > Then: >=20 > On old VM: >=20 > "take offline full backup (PG_DATA folder alone)=C2=A0 using OS command" >=20 > On new VM: > "Restore offline full backup (PG_DATA folder alone) using OS command" >=20 > 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. >=20 >=20 >=20 > --=20 > Adrian Klaver > adrian.klaver@aklaver.com >=20 >=20 >=20 --=20 Adrian Klaver adrian.klaver@aklaver.com =20 ------=_Part_2239750_223327809.1733944364447 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Team
As suggested from old server, post shutdown of DB, I d= id OS level dump of PG_DATA folder and had restored in the new server.

Any idea on how to install the older binar= y postgres 13.18 ( OS=3DAmazon Linux 2023.6.20241121) under a dedicated fol= der suffixed as the following e.g.) /usr/pgsql1318

System Admin had already installed newer version pgsql = 15.08 binaries in the  new server (OS=3D Amazon Linux 2023.6.202= 41121) in the folder "/usr/bin/"

We were quoted , OS =3D Amazon Linux = 2023.6.20241121 doesnot support postgres ver 15.10 (Community edition) unde= r its AWS-EC2.

Regards




=20
=20
On Wednesday, December 4, 2024 at 12:04:47 PM EST, = Adrian Klaver <adrian.klaver@aklaver.com> wrote:


=20 =20
On 12/4/24 04:42, Bharani SV-forum wr= ote:
> Team /Ron/Adrian
>
> Wann to reconfirm
> we have an setup = with
>
> new server will be with=
>
> will be following the follo= wing 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=3Dus-east-1 and= intended
> db as "postgresql 15.10 - community edn" = ] *
>
>   - "Restore o= ffline full backup (PG_DATA folder alone) using OS command"
> - create postgres unix userid
> - install post= gresql ver 15.10 binaries
> - setup respective env var= iable 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 <= br clear=3D"none">Mullane posted.

>=
>
> my question is
> a) is the above said steps is correct with the given existing a= nd
> proposed setup
> b) is thei= r any known issues using "cross over using pg_upgrade " option
> between the server's having below said operating system
> *- source =3D existing server with OS =3D *Amazon Linux rel= ease 2 (Karoo) "
> present in aws "us-east-1 region" = and along with postgresql ver 13.16.2 
> - commu= nity edn
> vs
> target - differen= t server *OS "Amazon Linux 2023 " in aws
> region=3Du= s-east-1 and intended db as "postgresql 15.10 - community edn"*
> *
> *
> *
> *
> On Tuesday, December 3, 2024 at 12:28:= 58 AM EST, Adrian Klaver
> <ad= rian.klaver@aklaver.com> wrote:
>
>
> On 12/2/24 17:23, Ron Johnson wrote:
>  > Adrian,
>  >>  > OP is moving to a new VM when migratin= g to PG 15.  When was the
>  > "cross-ser= ver" feature added to pg_upgrade?
>  >
>
> Moving to a new VM was not the issu= e, my mistake was thinking the OS
> version was stayin= g the same.
>
> Then:
>
> On old VM:
> > "take offline full backup (PG_DATA folder alone) = ; using OS command"
>
> On new V= M:
> "Restore offline full backup (PG_DATA folder alon= e) using OS command"
>
> Followe= d by installing new Postgres version could be dealt with using
> pg_upgrade. Once I was corrected on what was actually going on t= hen
> doing a dump/restore or logical replication beca= me better choices.
>
>
>
> --
> Adrian Kl= aver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
------=_Part_2239750_223327809.1733944364447--