public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
Date: Mon, 2 Dec 2024 20:23:59 -0500
Message-ID: <CANzqJaC1Uk4H=55vV_jbFYMuD1f9Bb_4Y9WKvkZA3bt92bEUnw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CANzqJaAda4nZbkG=c+72ry5GdaxrJ6Jzr6fz1quhq8tTfaX1Pg@mail.gmail.com>
<[email protected]>
<[email protected]>
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 PM Adrian Klaver <[email protected]>
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 PM Bharani SV-forum
> >> <[email protected] <mailto:[email protected]>> wrote:
> >>
> >> Team
> >> Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
> >> ver 15.X
> >>
> >> Env = 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 = 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
> >> 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 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.
> >
> > 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 <Redacted>, and butter sauce.
> >> Don't boil me, I'm still alive.
> >> <Redacted> lobster!
> >
>
> --
> Adrian Klaver
> [email protected]
>
>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (61+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
In-Reply-To: <CANzqJaC1Uk4H=55vV_jbFYMuD1f9Bb_4Y9WKvkZA3bt92bEUnw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox