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 1tIHeD-00DOzp-6v for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 01:24:17 +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 1tIHeA-005jdT-OU for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 01:24:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tIHeA-005jdK-67 for pgsql-general@lists.postgresql.org; Tue, 03 Dec 2024 01:24:15 +0000 Received: from mail-oi1-x22b.google.com ([2607:f8b0:4864:20::22b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIHe8-000k8R-Jk for pgsql-general@postgresql.org; Tue, 03 Dec 2024 01:24:14 +0000 Received: by mail-oi1-x22b.google.com with SMTP id 5614622812f47-3ea60f074c3so2830358b6e.1 for ; Mon, 02 Dec 2024 17:24:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733189051; x=1733793851; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=P8DWzyu/9WloL5peZ4mLbDCEq6n+JdslAd+Qwn1AqY0=; b=mzPV2MDtJPClLgV2yn/A/WsX7GAJufzgInmM+tbwa2lBms3vxsPs83WnfE+hYI71dP IT4x7BMAYNAToxp9Jp37jv2tHKeur90JPc1fi6LU5FS8OlhyHANUoOfk35ACDIhdQv7D cgkXQq75OERUwFYUGMfoUriJL0gJjuRyBgREhqhYKddmznCU878t5VZvRlUkOo476SqY 6YBfdWELituUNMsOS/XbKDg3scmIHwSNzF8SGOmGvjDra4wRLIiqVUGQqercgOsAEI+K NrrAX8f0uKISKRaIyK3bjaFTB+wVHvjcfWqgqD0SS/LRlyNY3KAF4XH94P4Np2CsfPmL wQTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733189051; x=1733793851; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=P8DWzyu/9WloL5peZ4mLbDCEq6n+JdslAd+Qwn1AqY0=; b=q+PZp2xGho1Yzpuuiy7daF4CSQiN8W/MVn0zHTsdeZr76qANFVivRMESGxdafj/PcE uK6S8XZEsxT4cjVtA8/j5V+sngTY61d1NdlTfLOJH5DER/4CCzDDUC38neb9J5aH3BrG ZeAwcZ/syFtuh6A+tpl06KQMQnoAkvx8O018G2NZJWj08JcJABjN2dsVq3giPB4fubzG vm76/sUVJIR3WMHXoi5iTi/pGNLlZa6N2ORHWXGejqSlq7rj7uDKa8HzfoMlSqo/ypbC /F0sZMFHgoU8kWbyfO36iYdL3rQybNbBTeK5eAs/0aqWyHjeafaXXTj2e7ytwidKndyX 581w== X-Gm-Message-State: AOJu0Yx0WvaALZ7B0hXKCEbMmXA0c6N/SOTcOf9N6wZhiWjFQQ2kNsnU SvqezsmGq3hIt3MnEJgESD5c6jHTCDYoCS+7SpEhDhbV/XCqTqsiKI2dUQUvGx3GpuzIyjDDLAQ Cn+W+1X5gV99iv/MotyBhU2xTXAG5pw== X-Gm-Gg: ASbGnctbFryndZ+G22UC/xOE0m04RQ6Iw9j18+nIj0xk9qf4gGeRnQ08GrBOoOr8rIi ZUDu4uo3rNTlegsVg2NmCnjgt52q3CLK9yqzTRsB+D7QMzFgIGCy9NbYfGpJ688VYWA== X-Google-Smtp-Source: AGHT+IFJYPbSbO0kG9S1vj4wW25lI0wMl0Idd8QNOlVoCx2lmzZF+sGhfUC8vLWlVHXYGxJLZk6Md11Fu+du+dxwhc0= X-Received: by 2002:a05:6808:3992:b0:3ea:6533:f1b2 with SMTP id 5614622812f47-3eae5059b7fmr529702b6e.30.1733189050068; Mon, 02 Dec 2024 17:24:10 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> From: Ron Johnson Date: Mon, 2 Dec 2024 20:23:59 -0500 Message-ID: Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a874910628538563" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a874910628538563 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Adrian, OP is moving to a new VM when migrating to PG 15. When was the "cross-server" feature added to pg_upgrade? On Mon, Dec 2, 2024 at 5:48=E2=80=AFPM Adrian Klaver wrote: > 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 > >> > wrote: > >> > >> Team > >> Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X = to > >> ver 15.X > >> > >> Env =3D EC2 based Community PostgreSQL Ver 13.16.2 > >> > >> we will be performing upgrade 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 > >> *ASIS-existing server =3D EC2 with Community PostgreSQL Ver 13.16.= 2* > >> - ensure to capture all the pre.req meant for ver 15.10 are being > >> met. > >> - shutdown db. > >> - take offline full backup (PG_DATA folder alone) using OS comman= d > >> > >> *Proposed-new EC2 server (with new Operating System version along > >> Postgres Ver 15.10 Binaries)* > >> - install postgres 15.10 binaries > >> - 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 step to upgrade postgres from ver > >> 13.16.2 to 15.10 > >> > >> please guide me, if i have missed any steps in the abovesaid proce= ss > >> > >> To start new DB features, planning to rollout out the following > >> 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 upgrading, one must use > >> pg_dump/pg_restore OR Logical Replication. > > > > Really? > > > > Then this: > > > > https://www.postgresql.org/docs/current/pgupgrade.html > > > > must be random nose. > > Oh yeah, that was smooth. > > Second attempt: > > ... must be random noise. > > > > >> > >> -- > >> Death to , and butter sauce. > >> Don't boil me, I'm still alive. > >> lobster! > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000a874910628538563 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Adrian,

OP is moving t= o a new VM when=C2=A0migrating to PG 15.=C2=A0 When was the "cross-ser= ver" feature added to pg_upgrade?

On Mon, Dec 2, 2024 at 5:48=E2= =80=AFPM Adrian Klaver <adr= ian.klaver@aklaver.com> wrote:
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:<= br> >>
>> =C2=A0=C2=A0=C2=A0 Team
>> =C2=A0=C2=A0=C2=A0 Pl Help in vetting my steps for Postgres DB upg= rade from 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.1= 6.2
>>
>> =C2=A0=C2=A0=C2=A0 we will be performing upgrade of our EC2 server= too along with new
>> OS.
>>
>> =C2=A0=C2=A0=C2=A0 Need help in vetting my steps for Postgres DB u= pgrade 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 Po= stgreSQL Ver 13.16.2*
>> =C2=A0=C2=A0=C2=A0 - ensure to capture all the pre.req meant for v= er 15.10 are being
>> met.
>> =C2=A0=C2=A0=C2=A0 - shutdown db.
>> =C2=A0=C2=A0=C2=A0 - take offline full backup (PG_DATA folder alon= e)=C2=A0 using OS command
>>
>> =C2=A0=C2=A0=C2=A0 *Proposed-new EC2 server (with new Operating Sy= stem version 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 o= f postgres 15.10
>> =C2=A0=C2=A0=C2=A0 -=C2=A0 Restore offline full backup (PG_DATA fo= lder alone) using OS
>> command
>> =C2=A0=C2=A0=C2=A0 -=C2=A0 start performing pg_upgrade step to upg= rade postgres 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 abovesaid process
>>
>> =C2=A0=C2=A0=C2=A0 To start new DB features, planning to rollout o= ut 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 us= e
>> pg_dump/pg_restore OR Logical Replication.
>
> Really?
>
> Then this:
>
> https://www.postgresql.org/docs/current/p= gupgrade.html
>
> must be random nose.

Oh yeah, that was smooth.

Second attempt:

... must be random noise.

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

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



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