public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Nikhil Shetty <[email protected]>
Cc: Jack DeVries <[email protected]>
Cc: [email protected]
Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
Date: Thu, 14 Jul 2022 16:34:55 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <Yso7pu6UIJFvx/[email protected]>
References: <CAFpL5Vx7Z676aa+Gyg6igONDDg+Pmoy=vyZ1Vc0YiZKc-Cyp1A@mail.gmail.com>
<CAFpL5Vxastip0Jei-K-=7cKXTg=5sahSe5g=om=x68NOX8+PUA@mail.gmail.com>
<[email protected]>
<CAFpL5VxzjWnfBR0yPUmt+GBsVWRfi_m5dk4M-694dcGn7EqcrQ@mail.gmail.com>
<Yso7pu6UIJFvx/[email protected]>
On Sat, Jul 9, 2022 at 10:38:30PM -0400, Bruce Momjian wrote:
> > (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!
>
> I have written the attached patch to document this.
Patch applied to all supported versions.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
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], [email protected]
Subject: Re: Fwd: Adding more detail to pg_upgrade documentation
In-Reply-To: <[email protected]>
* 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