public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nikhil Shetty <[email protected]>
To: Jack DeVries <[email protected]>
Cc: [email protected]
Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
Date: Sat, 4 Jun 2022 15:08:58 +0530
Message-ID: <CAFpL5VxzjWnfBR0yPUmt+GBsVWRfi_m5dk4M-694dcGn7EqcrQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAFpL5Vx7Z676aa+Gyg6igONDDg+Pmoy=vyZ1Vc0YiZKc-Cyp1A@mail.gmail.com>
	<CAFpL5Vxastip0Jei-K-=7cKXTg=5sahSe5g=om=x68NOX8+PUA@mail.gmail.com>
	<[email protected]>

Hi Jack,

I followed the same steps multiple times but each time, slot had to be
recreated.

The slots under directory pg_replslot are not created in the new cluster
during pg_upgrade.

Thanks and Regards,
Nikhil

On Sat, 4 Jun 2022 at 1:48 AM, Jack DeVries <[email protected]> wrote:

> Hi Nikhil,
>
> From the pgupgrade docs:
>
> > 9. Prepare for standby server upgrades
> >
> > If you are upgrading standby servers using methods outlined in section
> > Step 11, verify that the old standby servers are caught up by running
> > pg_controldata against the old primary and standby clusters. Verify
> > that the “Latest checkpoint location” values match in all clusters.
> > (There will be a mismatch if old standby servers were shut down before
> > the old primary or if the old standby servers are still running.)
> > Also, make sure wal_level is not set to minimal in the postgresql.conf
> > file on the new primary cluster.
>
> (source: https://www.postgresql.org/docs/devel/pgupgrade.html)
>
> I'm a new contributor so please forgive me if I'm on the wrong track,
> but if you follow this step, won't you also be ensuring that replication
> slots do not need to be migrated, since you've just ensured that standby
> clusters are in sync with the primary cluster? Please let me know if I'm
> missing anything!
>
> Thank You,
> Jack DeVries
>

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], [email protected], [email protected]
  Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
  In-Reply-To: <CAFpL5VxzjWnfBR0yPUmt+GBsVWRfi_m5dk4M-694dcGn7EqcrQ@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