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 1tIGE6-00DFD0-4w for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 23:53:14 +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 1tIGE3-004xcp-Ap for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 23:53:12 +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 1tIGE2-004xc3-St for pgsql-general@lists.postgresql.org; Mon, 02 Dec 2024 23:53:12 +0000 Received: from sonic309-21.consmr.mail.ne1.yahoo.com ([66.163.184.147]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIGE0-000jfk-Ep for pgsql-general@postgresql.org; Mon, 02 Dec 2024 23:53:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733183586; bh=AUSyzrpyc5c1PYXGG9UjJkL0dN43ANRRRgVmuFJln3Y=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=cWniTaKTDSwz9d3GspVpFQOEIuQ0eogyTT+tHpf7qf5ipXEjR+7jNy+fAru+8J5sDnIKONUapvqvviC+iVb/VncV+k7id3Ea0QAQeHuAx3JL8fmbO5ATjplLcLR60vyioFMqRwVfKGJcU5lqGDgpb486nWDrzCiGbw3tx7SaMakmj3oG++ONKLtH1E+4PMd4WTOg5gvNJDL1YbIubHRRkAl9QFzOR1qBDnkDR/S1UX4JSq5wE7em6KqhAXQdEqHRMk781s27pGxOygQ/BvWGZO9qRWhxs0wn4AucXlwveL74Z+bIfjEwHnNkTs5TuyD40zLkm8zizYW8CkGCchLfHA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1733183586; bh=o3+zX8DUT9uE+S+9Q9vYGsVG93AjJXVfRNQbDXWLUKw=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=Spk/DoF7q/N7E11qI32BAjPi86liUv37mk/rqRrbvztK6TunfPN+cdQaqUsmWtfUx0i1S6+12GAXlSi22zVZ+QcxTWmUqstGpr8MiBySjGy6By5JWMm1u6a2hhxGrMpXwtEujbpjy1Ie81CPhvEi+jNhXK/JhqSMChe3sj540gKJPWleYmd+PUfaecLPsZLOq/6UkTIN3qaCdHXstcL4s2R0+yMQInu1pMkKNIfGGTwzVtJ2g1nheokgU5uvH+pfUHvIRQVOF+ZkdcY0Dx+VWJ8TE/2Uy655v1bEjz2lptOJnhLQPj6W0tLPtPgG4Fu690v3I0r2xXfjcMTDeng9xQ== X-YMail-OSG: B.ywogQVM1lQs9Q0px.X9x4IHBsClwWLAfX3a.FGQ2DlnB9eobCR4_0W2eyAfz0 8NHyVpycVzPTKrBQ_87ZamaH0ZeMcHYkE2zBFo4H4wst1xRIgjVs0r_xFRE_0kA.p2xVwhJe1NS_ 4hh3UU8P40yPy2p.A2H28rrwSLWbG.cV68jy1MklTSYPRyGEaPTvyLVvjfgsKX8Y9Fg4if7UQeEW pRWJt25b_63qOP7jjOTJWLM4wTFkn4BvaDLu8kEQuAzj9gP2SwwZRBfoGA2QoU5NuM.s0wBmvOUZ 4.oL8dr7qOsaec.a6yj8wGt.10bOfYm7A0y5kZiE6x4.aCCM2IOq_OTfuFQAQEF7w0sUjPESz1lI 2PcjLt5dXDFOghmD.ag8Aad.PmvUbvniEwF9itclZaPyiaUVjt6xv5jEa3nX029On9UnVISD0Y9u 5Od80JTH4LB20K0CpZGXddYBAIHy7D9hTstAukZLl15zndyxB9ZOXA1_y85nkPUy8COEt7Z4zsnO 5YWgI8qBocI7y6g2km9cis9nHcHtadeaNIzre.GmzrwydQD8E7OhKUYYwSvJkqKaJR1.DH.MAUBk iZJFV1U9zMeTS0A6uGL30UjjewZ2jZifO0BxVIWC2KwFK3I_2tyCUnqBiFSxuaDhukn17VL03xZ4 2P6eWbOL8j_9y1gZUgO3BI_mFqgBMINxkZGipNR34M5xZR.gcQ6cFegWM6J8NbtgVva8QTqysOT5 Dxx9R0MQMcRmJ1Wm4tOUuj6Ylk_04vFRCwiyWAM52Wk7pRdMcCjeOWgiakTQO_OEtFFTqgdwuPe6 98cEhn.ePS6T1IRlhMawnLo2cHMSekFOT3SvAN7zu9Ces.P56oUq2PmDvy.ojD.o5xHSISN4DMxP P7bQNDl5ufVYMw1nHzXWtmXLkAv4ex3dVbJ46n3WMLke6x7EdavQt.PtOjSDnIOjM4IipzXqLNtY vh1ji2e2ByeacZKVPjc.drL3KK.VgnZzo9Cb_Uai9_nML8gzcXNUZ2As0M81zQVmJHHHQcsPl5ME .KAHV3SsxUYZQ0KdcHBWN7VCxPOfyIqAMiEEXe2Ny3WDMaARTtQlNxuRWKYEIPFINi8GywT_GI.a 3uIpsc2BBHrzZ0Irb5hjBs.n0lXYRmvCfVOWja5LR_ypn85NyZ1W8ivwKXKUxjdLj9zOt.sJBcQm GZNMQ7sIyoEVjqR7k717sTEZioloCaKQ0frjuIUrCwi44ypMHRavGrzDYk9zM9P26VG.S7JXquOJ rkJsm5nzC_NjGP2vB4D83l5P6vGUHNMZLqMM_S3ITxt7u0G2HfIvmjIbYLN2Wdu6MII55AkzkwBw WRumiOYRoimR8mmComfgJsJPE04dI0eTJj_MqI5A56g3kOJAZZib8wUISfUhd9dKCeiiNcSqhxxy Dw1zh2ixKuNtlLCj95WsEmeb5GLWxbLVCEusjT.A7NaeZJY2ghzX__DLox2WdNnzlmc6.w34jleX oSyt33vmf3g.VZyRua9T5.5zfIhHfjsRZfwGZXJxMBTmGDfSUcbP2I3_UXoO3RxVqJ.MM5xMPbCd ntTpTu9gyfp03LjAkwkpcTtvLZXoi3BggAmfIAzN2zSgJdgRIxj1DVpLhs.O8jIxlWf7r5fgjAqe NAWjwF8JTMH7AmrAKyACmICof.6xuGD1.v4QASyYQPdyjyyhGc6jNHVL2tTB0YGLcj.y1NBS6_jD XiDVwNEJ_gSGB2WgBXnA1N88C3n0s7bnpPwhwdGkMGwzxtVGI3WnaTnNqyK3FEo57smpJoWlDnl_ 66acrRWanx9q6l3qO1alm3c4ATioHXM_ER1EcOSlkhbptRWPzBTHsZATsZbOjnJxBxRbtqtUqq14 hRUhQKj3JK590bGT9YC_obMM9x_q3bPVu13R5.D5dunzhYoVeV_XeLQ5ZHDWLHRXsNpoq1Ab33f9 kT3BvkOu54x3VrCDyZp62y_phz9k9p_4vBGZrwcRZWKQMy7ClbttxXL27qD30SFZvBNaHmCwZ57T 8tZDbB4yQoUespDOBX_2GN.UZN4mbEJ9S_rrRB3JZq9bXUdJAMKlMTgaxKsPlu.iRKQHF4As0Dm5 XYQ7HJr7S5Puiomj5XQcyWT46OKo0sBYqmpRORrJLNcuxgBW7cuKK_Bt_Det.zBJuYOFJHc9mFx6 tqr_NUKZ16iJp9K9Esotk9gHAu.nctP4Nu2g9yI1bWW0o59Zh4Lct7pymqJvTI20_BVDpGa45Ls1 OKruAhnrWnua01QL5XJxzED3RueYrvsrQldhRDkUjgntB2mJi8Kcqn5coo5xd43CXbjk1SUKNVdu BKRRZ888hDAG0d_irzz8dlDGf5RWr X-Sonic-MF: X-Sonic-ID: 6d192985-91a4-4ea9-aad7-d970e147fbfc Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ne1.yahoo.com with HTTP; Mon, 2 Dec 2024 23:53:06 +0000 Date: Mon, 2 Dec 2024 23:52:59 +0000 (UTC) From: Bharani SV-forum To: Ron Johnson , pgsql-general , Adrian Klaver Message-ID: <54665410.4461273.1733183579920@mail.yahoo.com> In-Reply-To: <32763ce5-76e6-454d-bd64-53db8b2b9af6@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> <1760813407.5166251.1733182880136@mail.yahoo.com> <32763ce5-76e6-454d-bd64-53db8b2b9af6@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_4461272_455719639.1733183579918" X-Mailer: WebService/1.1.22941 YMailNorrin Content-Length: 16026 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_4461272_455719639.1733183579918 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Adrian Proposed new Server is intended to have higher OS Version (centos ver 9.0) = and higher Postgres Version 15.10 Does logical replication will have issues , if the existing asis server is = having Postgres ver 13.16.2 with Cent Os 7.0=C2=A0with the new server havin= g higher OS version Centos Ver 9.0 and then propose to have the Postgres to= be upgraded=C2=A0from ver 13.16.2 to 15.10 Hope u have understood my question On Monday, December 2, 2024 at 06:47:10 PM EST, Adrian Klaver wrote: =20 =20 On 12/2/24 15:41, Bharani SV-forum wrote: > Ron/Adrian > Thanks for your input. > Your suggestion is >=20 > *option#1* >=C2=A0 =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 being = =C2=A0met. >=C2=A0 =C2=A0 =C2=A0 =C2=A0- enable logical replication tagged to proposed= new EC2 server=20 No, logical replication !=3D pg_upgrade process. > (with newer Higher OS Version ). >=20 >=20 > Proposed-new EC2 server (with new Operating System version along >=C2=A0 =C2=A0 =C2=A0 Postgres Ver 13.16.2 and 15.10 Binaries)* >=C2=A0 =C2=A0 =C2=A0 =C2=A0- install postgres 13.16.2 binaries >=C2=A0 =C2=A0 =C2=A0 - have postgres setup on par with existing setup and = having proper=20 > logical replication Again, no. >=C2=A0 =C2=A0 =C2=A0 - install postgres 15.10 binaries >=C2=A0 =C2=A0=C2=A0 =C2=A0 - ensure to DISABLE auto startup and shutdown o= f postgres 13.16.2 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 - ensure to DISABLE auto startup and shutdown = of postgres 15.10 >=C2=A0 =C2=A0 =C2=A0 - start postgres db ver 13.16.2 and ensure all are go= od. no errors=20 > in postgres log file >=C2=A0 =C2=A0 =C2=A0 -=C2=A0 start performing pg_upgrade step to upgrade p= ostgres from ver=20 > 13.16.2 to 15.10 >=20 > pl Vet the newer steps (revised version). I don't know how much clearer it can be, follow the step by step=20 instructions shown here: https://www.postgresql.org/docs/current/pgupgrade.html "These are the steps to perform an upgrade with pg_upgrade: [...] " >=20 >=20 > Regards > Bharani >=20 > On Monday, December 2, 2024 at 05:48:19 PM EST, Adrian Klaver=20 > wrote: >=20 >=20 > On 12/2/24 14:46, Adrian Klaver wrote: >=C2=A0 > On 12/2/24 14:31, Ron Johnson wrote: >=C2=A0 >> On Mon, Dec 2, 2024 at 5:18=E2=80=AFPM Bharani SV-forum >=C2=A0 >> =20 > > wrote: >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 Team >=C2=A0 >> =C2=A0=C2=A0=C2=A0 Pl Help in vetting my steps for Postgres DB u= pgrade from Ver 13.X to >=C2=A0 >> =C2=A0=C2=A0=C2=A0 ver 15.X >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 Env =3D EC2 based Community PostgreSQL Ver 13= .16.2 >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 we will be performing upgrade of our EC2 serv= er too along with new >=C2=A0 >> OS. >=C2=A0 >> >=C2=A0 >> =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=C2=A0 to ver 15.X >=C2=A0 >> =C2=A0=C2=A0=C2=A0 *ASIS-existing server =3D EC2 with Community = PostgreSQL Ver 13.16.2* >=C2=A0 >> =C2=A0=C2=A0=C2=A0 - ensure to capture all the pre.req meant for= ver 15.10 are being >=C2=A0 >> met. >=C2=A0 >> =C2=A0=C2=A0=C2=A0 - shutdown db. >=C2=A0 >> =C2=A0=C2=A0=C2=A0 - take offline full backup (PG_DATA folder al= one)=C2=A0 using OS command >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 *Proposed-new EC2 server (with new Operating = System version along >=C2=A0 >> =C2=A0=C2=A0=C2=A0 Postgres Ver 15.10 Binaries)* >=C2=A0 >> =C2=A0=C2=A0=C2=A0 - install postgres 15.10 binaries >=C2=A0 >> =C2=A0=C2=A0=C2=A0 - ensure to DISABLE auto startup and shutdown= of postgres 15.10 >=C2=A0 >> =C2=A0=C2=A0=C2=A0 -=C2=A0 Restore offline full backup (PG_DATA = folder alone) using OS >=C2=A0 >> command >=C2=A0 >> =C2=A0=C2=A0=C2=A0 -=C2=A0 start performing pg_upgrade step to u= pgrade postgres from ver >=C2=A0 >> =C2=A0=C2=A0=C2=A0 13.16.2 to 15.10 >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 please guide me, if i have missed any steps i= n the abovesaid process >=C2=A0 >> >=C2=A0 >> =C2=A0=C2=A0=C2=A0 To start new DB features, planning to rollout= out the following >=C2=A0 >> =C2=A0=C2=A0=C2=A0 feature's alone >=C2=A0 >> =C2=A0=C2=A0=C2=A0 a) TLE extension for password compliance >=C2=A0 >> =C2=A0=C2=A0=C2=A0 b) parallelize vacuum jobs to utilize -j opti= on >=C2=A0 >> >=C2=A0 >> >=C2=A0 >> To migrate from one server to another while upgrading, one must = use >=C2=A0 >> pg_dump/pg_restore OR Logical Replication. >=C2=A0 > >=C2=A0 > Really? >=C2=A0 > >=C2=A0 > Then this: >=C2=A0 > >=C2=A0 > https://www.postgresql.org/docs/current/pgupgrade.html=20 > >=C2=A0 > >=C2=A0 > must be random nose. >=20 > Oh yeah, that was smooth. >=20 > Second attempt: >=20 > ... must be random noise. >=20 >=20 >=C2=A0 > >=C2=A0 >> >=C2=A0 >> -- >=C2=A0 >> Death to , and butter sauce. >=C2=A0 >> Don't boil me, I'm still alive. >=C2=A0 >> lobster! >=C2=A0 > >=20 > --=20 > Adrian Klaver > adrian.klaver@aklaver.com >=20 >=20 >=20 --=20 Adrian Klaver adrian.klaver@aklaver.com =20 ------=_Part_4461272_455719639.1733183579918 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Adrian

Pro= posed new Server is intended to have higher OS Version (centos ver 9.0) and= higher Postgres Version 15.10
=
Does logical replication w= ill have issues , if the existing asis server is having Postgres ver 13.16.= 2 with Cent Os 7.0 
with t= he new server having higher OS version Centos Ver 9.0 and then propose to h= ave the Postgres to be upgraded 
from ver 13.16.2 to 15.10

Hope u have understood my question

=20
=20
On Monday, December 2, 2024 at 06:47:10 PM EST, Adr= ian Klaver <adrian.klaver@aklaver.com> wrote:


=20 =20
On 12/2/24 15:41, Bharani SV-forum wr= ote:
> Ron/Adrian
> Thanks for yo= ur input.
> Your suggestion is
> =
> *option#1*
>   ASIS-= existing server =3D EC2 with Community PostgreSQL Ver 13.16.2*
> -  ensure to capture all the pre.req meant for ver 15.10 ar= e being  met.
>       - enabl= e logical replication tagged to proposed new EC2 server
=
No, logical replication !=3D pg_upgrade process.

> (with newer Higher OS Version ).
>
>
> Proposed-ne= w 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 replicati= on

Again, no.

>      - install postgres 15.10 binaries
>       - ensure to DISABLE auto star= tup and shutdown of postgres 13.16.2
>    &n= bsp;   - ensure to DISABLE auto startup and shutdown of postgres 15.10=
>      - start postgres db ver 13.16.2= and ensure all are good. no errors
> in postgres log= file
>      -  start performing p= g_upgrade step to upgrade postgres from ver
> 13.16.2= to 15.10
>
> pl Vet the newer s= teps (revised version).

I don't know h= ow much clearer it can be, follow the step by step
instr= uctions shown here:

https://www.postgresql.org/docs/current/pgupgrade.h= tml

"These are the steps to perfor= m an upgrade with pg_upgrade:

[...]

"
&= gt;
>
> Regards
> Bharani
>
> On Monday, D= ecember 2, 2024 at 05:48:19 PM EST, Adrian Klaver
> &= lt;adrian.klaver@aklaver.com> wrote:
>
>
> On 12/2/24 14:4= 6, Adrian Klaver wrote:
>  > On 12/2/24 14:31,= Ron Johnson wrote:
>  >> On Mon, Dec 2, 20= 24 at 5:18=E2=80=AFPM Bharani SV-forum
>  >>= ; <esteembsv-forum@yahoo.com <mailto:esteembs= v-forum@yahoo.com>
> <mailto:esteembsv-forum@ya= hoo.com>> wrote:
>  >>
>  >>     Team
> = ; >>     Pl Help in vetting my steps for Postgres DB u= pgrade from Ver 13.X to
>  >>   &= nbsp; ver 15.X
>  >>
>=   >>     Env =3D EC2 based Community PostgreSQL V= er 13.16.2
>  >>
>&nbs= p; >>     we will be performing upgrade of our EC2 ser= ver too along with new
>  >> OS.
>  >>
>  >>  &= nbsp;  Need help in vetting my steps for Postgres DB upgrade from Ver = 13.X
>  >>     to ver 15.X>  >>     *ASIS-existing serv= er =3D EC2 with Community PostgreSQL Ver 13.16.2*
>&nb= sp; >>     - ensure to capture all the pre.req meant f= or ver 15.10 are being
>  >> met.
>  >>     - shutdown db.
>  >>     - take offline full backup (P= G_DATA folder alone)  using OS command
>  &g= t;>
>  >>     *Proposed-n= ew EC2 server (with new Operating System version along
&g= t;  >>     Postgres Ver 15.10 Binaries)*
>  >>     - install postgres 15.10 b= inaries
>  >>     - ensure t= o DISABLE auto startup and shutdown of postgres 15.10
>= ;  >>     -  Restore offline full backup (PG= _DATA folder alone) using OS
>  >> command<= br clear=3D"none">>  >>     -  start perf= orming pg_upgrade step to upgrade postgres from ver
>&= nbsp; >>     13.16.2 to 15.10
>&n= bsp; >>
>  >>     plea= se guide me, if i have missed any steps in the abovesaid process
>  >>
>  >>  &= nbsp;  To start new DB features, planning to rollout out the following=
>  >>     feature's alone>  >>     a) TLE extension fo= r password compliance
>  >>   &nb= sp; b) parallelize vacuum jobs to utilize -j option
>&= nbsp; >>
>  >>
>=   >> To migrate from one server to another while upgrading, one = must use
>  >> pg_dump/pg_restore OR Logica= l Replication.
>  >
>&nbs= p; > Really?
>  >
>&nb= sp; > Then this:
>  >
>= ;  > https://www.postgres= ql.org/docs/current/pgupgrade.html
> <https://www.postgresql.org/docs/current/p= gupgrade.html>
>  >
&= gt;  > must be random nose.
>
> Oh yeah, that was smooth.
>
> Second attempt:
>
> ... mu= st be random noise.
>
>
>  >
>  >>
>  >> --
>  >> Deat= h to <Redacted>, and butter sauce.
>  >&= gt; Don't boil me, I'm still alive.
>  >> &= lt;Redacted> lobster!
>  >
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <m= ailto:adrian.klaver@aklaver.com>

>
>= ;
>

--
Adrian Klaver
adrian.klave= r@aklaver.com


<= br clear=3D"none">
------=_Part_4461272_455719639.1733183579918--