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 1tIG2l-00DEJU-DP for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 23:41:31 +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 1tIG2i-004oPQ-Tg for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 23:41:30 +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 1tIG2i-004oPG-G5 for pgsql-general@lists.postgresql.org; Mon, 02 Dec 2024 23:41:29 +0000 Received: from sonic304-22.consmr.mail.ne1.yahoo.com ([66.163.191.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIG2f-000jYb-MQ for pgsql-general@postgresql.org; Mon, 02 Dec 2024 23:41:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733182883; bh=c37xwuiPLUwTN2AMf60gLkFvDE27/zueUkwKvID8Czg=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=uh3EXmjPeO4AFfuqaQxgqyInkRXf5L1h8Id2yox3V45sgHNnvL4G57cMchFAydkuHD0rG7WRHkmYbPVsw/7D2VMd/FPWEZNwRO4UWOvqcDMWGJ8j+3OMMT0hW+iIGiLGgY0N1kVTAyv2B/ML+TdeecFrS4AL4KGHO6LAJ9wiuwr4wtKtcRYR1H36MjiRCWuAG57dGPRaUHBwudBp7IUDuEblV/0Cq7wJ/x41COfxysQs0CVnCmwGN3qm4NAYKuJIbFQKLS7iA7vZTniu488S8szXBbYWU/Mqj4gjCagrz1UnGSAYxs+4vbf51/6io5Edk+IdiDjofMN6ayGOIA1U7A== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733182883; bh=yduMrqTIaWnK1neQkajXbb0/ura2S+ILrS1JIl19ZXo=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=GYq+xQKpudYWr0N86hGs9MpHh+zf2XPucZLdkPVzLlAUkfifYCjkmyY+okaj0uSsTEFmmb1dWsFWZSG7cg03KUIwcY7ziYFn23a5nkvUC6dJsPIdxer+JPgJrHNFicrnWe5y2G07cTa51rGTfJT9z5g2+Ms1OlTWOBmBfTBsqRAV6lPAjZvMWggLZZse6FYZzdYLOoZrODzZ2Ew+IhoUem7tf0LXAql6AoKXkvxx4M7ApxNqVPlM9JI0OUTr4IRopI5eC/T6k1F+BOFjJ1QDFj+SVnboy/tz7JeE9acqvHC59a4hj5acl1o1r+hbyKXkyg5azNjTxR8ZUqAPHcE0ZQ== X-YMail-OSG: V51_At0VM1nu0zfisg_ELJ9wFLYBbDG6saIafilXMrwXOcTIORU7IVi5NwmwSTe 0la62mKDcQCtTYfP0Z3GUpa4kOSG8lT6C0Fqs.JY6FlCF.Efcr3p0dtBNIyByq7ecBjOIdsVed1N 1Z5ro10tJpbMnM8KjOi25wZeJ7NfH4vjIr0GcHcndePsosdE.NcuTLT8ig3T2.CKFOZfE_KKkLLZ IIRQXejFwfZcaBZdji6uH1Rh_PFGXJMABokg_hEqVkq6A9NEfldD8Uk50Ex.E1E88_7VZzNcC938 AiKe0NxYSmiuUiWocYuJjDJr2oTSfUuA.6tI5jla6iH2giNuQtx8q3oDRkekcgxLlUOV4pfWTDwC TLzL_ZCkgPiosnwE2MktVQHb2Wl5wpydFnWhWxRwJePvoDJ6r9CvECBbnb5FAdqEdqgertoWjlgt YwcK.AHUqXkXyaeB_0LxmprM5sBCeDJYSybMj6WD00TarGzWYLqjqrlaPG..lH16zp5nal3qUi4U 4jULAPGqUsqBL5CLV207.v36AzN2TNqf4yPijpjiPsNj8BdcjIqQOBeN7Lbk3fI0bB0q4GbnBvTr ubB9nHd6gudLUK5IkTDNBJW7CBe8tcmecOtnz79wgky6jj8x16.OaQM_qFMrvdG8_wdRfmTfnwxg 8uO_OlVmQb.KiuiNuBcgljgm_GTgJzXAd0zp0QQUjH_Wr.WHk0x1c_l_XI5Qgz8asyxpCKjyTopr E9IuOkUq6HX2GrS8sZ8rkuGei..gGO0gm6Bu.3gx5FTEa9ft0FpbNRKj1wGt73RMVBmEhTWpsSO4 Fo6g.gb5BOYiKKMw1PrzmA4pa2MZ8E9kIOQ2naezlpBvSBWU6D2WHmvGcXysofFaa.7g3oHnthyr 8Ka8LOy6G.m2qYl.ecloID0YQ.iEb9e6iW6loO0ojapwS4xcxBLmUrlA4MDuw7nzCqFevJbO4JgA GKrdGhWK2BQ0lDajheM..NYRI6Jw6nqjfj09rCGyiUZW1aRtJ87wALCFyTKnbMWHkpXiZ.L1lD32 G9cz3S1F4OfvMPNJPJmuZji1pS2y0jzoI2hupJkICzbZi1Us057XjfweK6hI5hxayOMWzQZJZq60 rqmriq_Rr2E45Eyho5cm83sbZLY_BiyEXwh0ekHDFdSjxbRR7v08YfQoi_BnF_VhsbKZ0shoil7M odcqFXrA61uj0esNt0Ecl5wohvWC_HlUUqZwgatsA64uEqsOBDGX7w43C.TWjQRtfCN9YaiAegYw hevepRhVO7LCHBCYD2bWydLESOWg2f6GPuiU57fYd.UHBnuHqOARmGGrQXvwQyeQxv96Rgo.HYSz 0pW58OdPNKoasQmU8VyEL8jDqDCq69YwukL5yhlXwZIyahn9T7w_pyQYxi9CcXRtOFAacCE6_WxC nBLAbkGBrM8ifnxjEBMVlmVx1edYrAKjGH_qWvCKJbYoqtWlusLwt9HBPGEK2qW_bO.nmAXTMDYz I_KgpzJZVOxbBF1jKpSbdYBBCBVuCT7UW4TpA1DPkaHDGX1Gyz7Ymk_uhmRuezleaGwUQWED3jtX n_7IzT9lITrd4yblellQY0TLpM1BKUXWp7dsZFhDbrHhGdCpwmpOFUTBtObQRctsM_D_nkI0rNhH 8Sot4Q13uEXB23iz8kC810oZC8T6d0QQ_.FU3aFbyYl9b3sKrFOtwa_nfQfSN3rDI_xFqeAT.2sP mKZkmnSY2qDym7GIitu0JJAA9VnodYj8i0soHHje3_ywVcg_ewlaZoVKViaYBPhffbqhNwVAgXbu FW8XYy6yIS5gufwNELfSyBiCUQqvJZNHHJeZXMVhoymlCiK7CqT0Zth5B2GmVJv25VPQ4z1_IYS7 _8Wu3EUPJxOSFlfBcbXRcmiCKHXoO1kJOPfPrR6MZgyUjqayZMVOhRlCSV_m7kErLChJ4uEegISs CGOGSr_ndoOZS.OFCSC7RkTsV9ILSCulh_Vx2HzjikcqODAD3GY8fPlDTZPJshte269pO0oKb_rp KVd4L0zoP309K9K9eUBCi4rc1itUdPdMWPV4Ny64yxIqZMYSipk4iXc0qrrPbJDVSozynubOgHzB MJOUd3weEpGRwarLPHZhz3dVXvfS6EC3EePvmjFLDy4FRyMlBgWdU3qZpcFTG1KLZLYNzrVPDmEW QFuu.1AODo3uzNn7DYwcvu3Ucbbn88fM_8R6wKyRqZW1Oa1sRzg2X0fNVv4qXOip_XFMq_vDU1VU _RvZk9XIjbXjvNVXJLWyCKPeVX6qfJTnk0a1T6CihzuK2n_PSNVudFTHIfex6_mqr5RNAazYZgsb 9Cxd6dDT3z5Qi_J2pdioIMi9i5DescBH4xwXUPX_wso9Mou6RVzgetYLKM_U9K2Q- X-Sonic-MF: X-Sonic-ID: 33393b71-1a1f-4063-bc83-39303c493425 Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ne1.yahoo.com with HTTP; Mon, 2 Dec 2024 23:41:23 +0000 Date: Mon, 2 Dec 2024 23:41:20 +0000 (UTC) From: Bharani SV-forum To: Ron Johnson , pgsql-general , Adrian Klaver Message-ID: <1760813407.5166251.1733182880136@mail.yahoo.com> In-Reply-To: <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> 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> Subject: Re: 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_5166250_1728330932.1733182880134" X-Mailer: WebService/1.1.22941 YMailNorrin Content-Length: 13552 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_5166250_1728330932.1733182880134 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ron/AdrianThanks for your input.Your suggestion is option#1=C2=A0ASIS-existing server =3D EC2 with Community PostgreSQL Ver 13= .16.2*-=C2=A0 ensure to capture all the pre.req meant for ver 15.10 are bei= ng=C2=A0=C2=A0met. =C2=A0 =C2=A0 =C2=A0- enable logical replication tagged to proposed new EC2= server (with newer Higher OS Version ). Proposed-new EC2 server (with new Operating System version along =C2=A0 =C2=A0 Postgres Ver 13.16.2 and 15.10 Binaries)*=C2=A0 =C2=A0 =C2=A0= - install postgres 13.16.2 binaries =C2=A0 =C2=A0 - have postgres setup on par with existing setup and having p= roper logical replication=C2=A0 =C2=A0 =C2=A0 - install postgres 15.10 binaries=C2=A0=C2=A0 =C2=A0 - ensure= to DISABLE auto startup and shutdown of postgres 13.16.2 =C2=A0 =C2=A0 =C2=A0 - ensure to DISABLE auto startup and shutdown of postg= res 15.10=C2=A0 =C2=A0 - start postgres db ver 13.16.2 and ensure all are g= ood. no errors in postgres log file =C2=A0 =C2=A0 -=C2=A0 start performing pg_upgrade step to upgrade postgres = from ver=C2=A013.16.2 to 15.10 pl Vet the newer steps (revised version). RegardsBharani On Monday, December 2, 2024 at 05:48:19 PM EST, Adrian Klaver wrote: =20 =20 On 12/2/24 14:46, Adrian Klaver wrote: > On 12/2/24 14:31, Ron Johnson wrote: >> On Mon, Dec 2, 2024 at 5:18=E2=80=AFPM Bharani SV-forum=20 >> > wrote: >> >> =C2=A0=C2=A0=C2=A0 Team >> =C2=A0=C2=A0=C2=A0 Pl Help in vetting my steps for Postgres DB upgrade f= rom Ver 13.X to >> =C2=A0=C2=A0=C2=A0 ver 15.X >> >> =C2=A0=C2=A0=C2=A0 Env =3D EC2 based Community PostgreSQL Ver 13.16.2 >> >> =C2=A0=C2=A0=C2=A0 we will be performing upgrade of our EC2 server too a= long with new=20 >> OS. >> >> =C2=A0=C2=A0=C2=A0 Need help in vetting my steps for Postgres DB upgrade= from Ver 13.X >> =C2=A0=C2=A0=C2=A0 to ver 15.X >> =C2=A0=C2=A0=C2=A0 *ASIS-existing server =3D EC2 with Community PostgreS= QL Ver 13.16.2* >> =C2=A0=C2=A0=C2=A0 - ensure to capture all the pre.req meant for ver 15.= 10 are being=20 >> met. >> =C2=A0=C2=A0=C2=A0 - shutdown db. >> =C2=A0=C2=A0=C2=A0 - take offline full backup (PG_DATA folder alone)=C2= =A0 using OS command >> >> =C2=A0=C2=A0=C2=A0 *Proposed-new EC2 server (with new Operating System v= ersion along >> =C2=A0=C2=A0=C2=A0 Postgres Ver 15.10 Binaries)* >> =C2=A0=C2=A0=C2=A0 - install postgres 15.10 binaries >> =C2=A0=C2=A0=C2=A0 - ensure to DISABLE auto startup and shutdown of post= gres 15.10 >> =C2=A0=C2=A0=C2=A0 -=C2=A0 Restore offline full backup (PG_DATA folder a= lone) using OS=20 >> command >> =C2=A0=C2=A0=C2=A0 -=C2=A0 start performing pg_upgrade step to upgrade p= ostgres from ver >> =C2=A0=C2=A0=C2=A0 13.16.2 to 15.10 >> >> =C2=A0=C2=A0=C2=A0 please guide me, if i have missed any steps in the ab= ovesaid process >> >> =C2=A0=C2=A0=C2=A0 To start new DB features, planning to rollout out the= following >> =C2=A0=C2=A0=C2=A0 feature's alone >> =C2=A0=C2=A0=C2=A0 a) TLE extension for password compliance >> =C2=A0=C2=A0=C2=A0 b) parallelize vacuum jobs to utilize -j option >> >> >> To migrate from one server to another while upgrading, one must use=20 >> pg_dump/pg_restore OR Logical Replication. >=20 > Really? >=20 > Then this: >=20 > https://www.postgresql.org/docs/current/pgupgrade.html >=20 > must be random nose. Oh yeah, that was smooth. Second attempt: ... must be random noise. >=20 >> >> --=20 >> Death to , and butter sauce. >> Don't boil me, I'm still alive. >> lobster! >=20 --=20 Adrian Klaver adrian.klaver@aklaver.com =20 ------=_Part_5166250_1728330932.1733182880134 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ron/Adrian
Thanks for your input.
Your suggestion is

<= /span>
= option#1
 ASIS-existing server =3D EC2 with Com= munity PostgreSQL Ver 13.16.2*
-&n= bsp; ensure to capture all the pre.req meant for ver 15.10 are being <= /span> met.
     - enable logical repli= cation tagged to proposed new EC2 server (with newer Higher OS Version ).


Proposed-new EC2 server (with new Operating= System version along
    Postgres Ver 13.16.2 and 15.10 Binaries)*
     - install postgres 13.16.2 binaries
    - have postgres setup on par with existing setup and having = proper logical replication 
    - install po= stgres 15.10 binaries
     - ensure to= DISABLE auto startup and shutdown of postgres 13.16.2
 = ;     - ensure to DISABLE auto startup and shutdown of postgres 1= 5.10
    - sta= rt postgres db ver 13.16.2 and ensure all are good. no errors in postgres l= og file
  =   -  start performing pg_upgrade step to upgrade postgres from ve= r 13.16.2 to 15.10

pl Vet the newer steps (revised ve= rsion).


Regards
Bharani

<= /div> =20
=20
On Monday, December 2, 2024 at 05:48:19 PM EST, Adr= ian Klaver <adrian.klaver@aklaver.com> wrote:


=20 =20
On 12/2/24 14:46, Adrian Klaver wrote= :
> On 12/2/24 14:31, Ron Johnson wrote:
>> On Mon, Dec 2, 2024 at 5:18=E2=80=AFPM Bharani SV-forum
>> <esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>> wrote:
>= ;>
>>     Team
= >>     Pl Help in vetting my steps for Postgres DB upg= rade from Ver 13.X to
>>     ver 15.= X
>>
>>     = Env =3D EC2 based Community PostgreSQL Ver 13.16.2
>&g= t;
>>     we will be performing upgr= ade of our EC2 server too along with new
>> OS.>>
>>     Need= help in vetting my steps for Postgres DB upgrade from Ver 13.X
>>     to ver 15.X
>> &= nbsp;   *ASIS-existing server =3D EC2 with Community PostgreSQL V= er 13.16.2*
>>     - ensure to captu= re all the pre.req meant for ver 15.10 are being
>>= ; met.
>>     - shutdown db.
>>     - take offline full backup (PG_DATA = folder alone)  using OS command
>>
>>     *Proposed-new EC2 server (with new Opera= ting System version along
>>     Pos= tgres Ver 15.10 Binaries)*
>>     - = install postgres 15.10 binaries
>>   &nbs= p; - ensure to DISABLE auto startup and shutdown of postgres 15.10
>>     -  Restore offline full backup (= PG_DATA folder alone) using OS
>> command
>>     -  start performing pg_upgrade s= tep to upgrade postgres from ver
>>   &nb= sp; 13.16.2 to 15.10
>>
>> =     please guide me, if i have missed any steps in the above= said process
>>
>>  &n= bsp;  To start new DB features, planning to rollout out the following<= br clear=3D"none">>>     feature's alone
>>     a) TLE extension for password compliance>>     b) parallelize vacuum jobs to = utilize -j option
>>
>>
>> To migrate from one server to another while upgradi= ng, one must use
>> pg_dump/pg_restore OR Logical = Replication.
>
> Really?
>
> Then this:
> <= br clear=3D"none">> https://ww= w.postgresql.org/docs/current/pgupgrade.html
> > must be random nose.

Oh yeah, that was smooth.

Second a= ttempt:

... must be random noise.


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

--
Adrian Klaveradrian.klaver@aklaver.com



------=_Part_5166250_1728330932.1733182880134--