MIME-Version: 1.0
References: 
 <CAFpL5Vx7Z676aa+Gyg6igONDDg+Pmoy=vyZ1Vc0YiZKc-Cyp1A@mail.gmail.com>
 <CAFpL5Vxastip0Jei-K-=7cKXTg=5sahSe5g=om=x68NOX8+PUA@mail.gmail.com>
 <Yppsghp3z8pMsrDH@Jacks-MacBook-Pro.local>
In-Reply-To: <Yppsghp3z8pMsrDH@Jacks-MacBook-Pro.local>
From: Nikhil Shetty <nikhil.dba04@gmail.com>
Date: Sat, 4 Jun 2022 15:08:58 +0530
Message-ID: 
 <CAFpL5VxzjWnfBR0yPUmt+GBsVWRfi_m5dk4M-694dcGn7EqcrQ@mail.gmail.com>
Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
To: Jack DeVries <jdevries3133@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000c93b3a05e09c029a"
Archived-At: 
 <https://www.postgresql.org/message-id/CAFpL5VxzjWnfBR0yPUmt%2BGBsVWRfi_m5dk4M-694dcGn7EqcrQ%40mail.gmail.com>
Precedence: bulk

--000000000000c93b3a05e09c029a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 <jdevries3133@gmail.com> 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 =E2=80=9CLatest checkpoint location=E2=80=9D values match in a=
ll 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
>

--000000000000c93b3a05e09c029a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Jack,</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">I followed the same steps multiple times but each time, slot had to be r=
ecreated.</div><div dir=3D"auto"><br></div><div dir=3D"auto">The slots unde=
r directory pg_replslot are not created in the new cluster during pg_upgrad=
e.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks and Regards,<b=
r></div><div dir=3D"auto">Nikhil</div><div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Sat, 4 Jun 2022 at 1:48 AM, Jack De=
Vries &lt;<a href=3D"mailto:jdevries3133@gmail.com">jdevries3133@gmail.com<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left=
:1ex;border-left-color:rgb(204,204,204)">Hi Nikhil,<br>
<br>