Re: pg_upgrade and logical replication
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: vignesh C <vignesh21@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-09-21T09:05:55Z
Lists: pgsql-hackers
On Thu, Sep 21, 2023 at 4:39 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Wed, Sep 20, 2023 at 04:54:36PM +0530, Amit Kapila wrote: > > Also, the patch seems to be allowing subscription relations from PG > > >=10 to be migrated but how will that work if the corresponding > > publisher is also upgraded without slots? Won't the corresponding > > workers start failing as soon as you restart the upgrade server? Do we > > need to document the steps for users? > > Hmm? How is that related to the upgrade of the subscribers? > It is because after upgrade of both publisher and subscriber, the subscriptions won't work. Both publisher and subscriber should work, otherwise, the logical replication set up won't work. I think we can probably do this, if we can document clearly how the user can make their logical replication set up work after upgrade. > > And how > is that different from the case where a subscriber tries to connect > back to a publisher where a slot has been dropped? > It is different because we don't drop slots automatically anywhere else. -- With Regards, Amit Kapila.
Commits
-
pg_upgrade: Retrieve subscription count more efficiently.
- 73de50e13e39 17.0 landed
- 364509a2e7f9 18.0 landed
-
Fix random failure in 004_subscription.
- 677a45c4ae16 17.0 landed
-
Fix 004_subscription.pl to allow its usage in --link mode.
- f17529b71097 17.0 landed
-
Allow upgrades to preserve the full subscription's state.
- 9a17be1e244a 17.0 landed
-
Prevent startup of logical replication launcher during pg_upgrade
- 7021d3b17664 17.0 landed