On Sun, 2023-05-21 at 07:56 -0700, Mike Lissner wrote:
> > As far as I know it's impossible to reliably pg_upgrade a node
> > that has subscriptions and eventually resume logical
> > replication.
> >
>
>
> Should this go in the documentation somewhere? Maybe in the
> pg_upgrade notes? I still
> As far as I know it's impossible to reliably pg_upgrade a node that has
> subscriptions and eventually resume logical replication.
>
Should this go in the documentation somewhere? Maybe in the pg_upgrade
notes? I still don't understand the mechanism. You also say that:
> It's possible to make
On Sat, 20 May 2023, 05:56 Mike Lissner,
wrote:
>
> I'm still trying to understand what went wrong though. Putting a finer
> point on my question: Does pg_upgrade mess up disabled subscriptions?
>
yes, whether they're disabled or not. As far as I know it's impossible to
reliably pg_upgrade a
Thanks for the suggestions. I think in the future I'll do something like
this rather than try to re-use existing subscriptions.
I'm still trying to understand what went wrong though. Putting a finer
point on my question: Does pg_upgrade mess up disabled subscriptions?
On Fri, May 19, 2023 at
Please, use the following runbook.
1. Disable the subscription to pg10.
2. Disable Application Users on Publisher.
3. Drop all replication slots on Publisher (The upgrade can not be executed
if there are any replication slots)
4. Run RDS's upgrade (which runs pg_upgrade).
5. Recreate replication
I also am realizing belatedly that my solution of dropping the subscriber
probably won't work anyway, since I'd lose the changes on the publisher for
the duration of the upgrade. Maybe I could drop the subscription while
keeping the slot on the publisher, and then create a new subscription after
Hi all,
In AWS RDS, we are using logical replication between a postgresql 14
publisher and a postgresql 10 subscriber. The subscriber is rather old, so
yesterday I tried to update it using AWS's built in upgrade tool (which
uses pg_upgrade behind the scenes).
I did a pretty thorough test run