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 1tIExS-00D8YM-4h for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 22:31:58 +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 1tIExP-004FOt-FH for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 22:31:56 +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 1tIExP-004FOh-1n for pgsql-general@lists.postgresql.org; Mon, 02 Dec 2024 22:31:56 +0000 Received: from mail-oo1-xc36.google.com ([2607:f8b0:4864:20::c36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIExN-000j34-9N for pgsql-general@postgresql.org; Mon, 02 Dec 2024 22:31:55 +0000 Received: by mail-oo1-xc36.google.com with SMTP id 006d021491bc7-5ee8eaa1694so2103674eaf.0 for ; Mon, 02 Dec 2024 14:31:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733178711; x=1733783511; 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=BuVGOgFkLckSVqoWvDe9q4NN2tDkdISY1vMGfPbkkwg=; b=VkdmWyTSoa3huLNLHu7UbMyjOF8wcUG4b2sVEZaHZ/98TQYs0M5q9AbANpkMU4CouC baqZTWPyIc0TQWbQ2jBeeRvh9yc87fNo1M26/Rt3m3yH3CnFMlL+GiPera0QGmWkbaJg tmnOP0LlXHp4RXmk3mB6+KLm78RlvRWLuOZ7IeVJYpHYxy4YrIdm/1ZDAFXYtJh56zyn zbx3xNS29OrE/HfCG9RjH4d6vtht4B+m9i/GySvBcYLoQ02bszxhfqSufi2/+GmAlSpY 1/oV9d2I6fkEqVtmlI1DgyPkLoEzx606G6kw7WwWhiMUy/xawA1es1+7L9eglfLrHHsY lkrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733178711; x=1733783511; 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=BuVGOgFkLckSVqoWvDe9q4NN2tDkdISY1vMGfPbkkwg=; b=bOOmKz/nL95XZGMzZgT1ndhVMOtqEtz3e54MNFXeVofmaxQvoTD1VSSoKgh0ijVKQB dD1au7wWE2ojuxVeeaBRUWF8FMrZvB9gV84172gDaihYWZeh6UrXvhY3ZmzjRwhiSgF/ zaSXwyHPepwNxcW6Ia/JXQHnP6UOMx3TRUrEDyODRiGJS0Pg04z2Zm2mXzEFwi0Mo8pu UgRa0SNTTyECBhH9StegPbljlcwEDYorkMZg6UuwbvfwUbcIEfgmliSIYjAC2xgLdGYh 47eO6tbfsDhhZl3tQJeFFs1GCDaNQZEDPKFjXLaTwXxrEokVB9tJGQMD7WwyCqkb/7vS 7A9A== X-Gm-Message-State: AOJu0Yzm6zv0JNeBYEtHIbSp60L0H9YcFQNBjNw+ef3j6omxi/a6qGFP J/43mhIiICcs3pfIqeL2kbmhUW4ZTWX9rJplFdBxxli/hXdjxBgesjVnc3Df8pO1/f1vHYRjPK+ bYlIz74m/dfO0Olqrb2Vyt8Z4fd22AA== X-Gm-Gg: ASbGncthvVJxQnLX5kyPUGxeaI8aey6NGFtG0WEc0+nMIEWLzq7hBGaue+D1OV51Nkf miD6zhyujEGxUae2U0LEJFBmlO7fd9bEzY61Ukdy29SlSVmKtCBxdJCWvtIIxQExe3g== X-Google-Smtp-Source: AGHT+IEvtXpXTDsGYfVc2/xULL2XaJStwhNSW3xm21lFavX2AIaNzGtsGKgL0/xQbHt+ycYZ5bewKZiX7/NCEzZjf9I= X-Received: by 2002:a05:6830:2118:b0:718:ab4:8b70 with SMTP id 46e09a7af769-71dad6ceff8mr213890a34.22.1733178711185; Mon, 02 Dec 2024 14:31:51 -0800 (PST) MIME-Version: 1.0 References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> In-Reply-To: <564950518.5117550.1733177884387@mail.yahoo.com> From: Ron Johnson Date: Mon, 2 Dec 2024 17:31:40 -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="00000000000069a0620628511dc2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000069a0620628511dc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 command > > *Proposed-new EC2 server (with new Operating System version along Postgre= s > 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 process > > 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. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000069a0620628511dc2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Dec 2, 2024 at 5:18=E2=80=AFPM Bh= arani SV-forum <esteembsv-f= orum@yahoo.com> wrote:
Team
Pl Help in vettin= g 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 vet= ting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
=C2=A0
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)=C2=A0 using OS comm= and

Prop= osed-new EC2 server (with new Operating System version along Postgres Ver 1= 5.10 Binaries)
- install po= stgres 15.10 binaries
- = ensure to DISABLE auto startup and shutdown of postgres 15.10
<= div style=3D"font-family:"Helvetica Neue",Helvetica,Arial,sans-se= rif;font-size:16px" dir=3D"ltr">-=C2=A0 Restore offline f= ull backup=C2=A0(PG_DATA folder alone) using OS c= ommand
-=C2=A0 start performing pg_upgrade step to upgrade postgres from ver 13.1= 6.2 to 15.10

=
please guide me, if i have mis= sed any steps in the abovesaid process

= To start new DB features, planning to rollout out the following feature'= ;s alone
a) TLE exte= nsion for password compliance
= b) parallelize vacuum jobs to utilize -j option

To migrate fr= om one server to another while upgrading, one must use pg_dump/pg_restore O= R Logical Replication.

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