Re: pg_upgrade and logical replication
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <amit.kapila16@gmail.com>
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-21T23:06:21Z
Lists: pgsql-hackers
On Thu, Sep 21, 2023 at 02:35:55PM +0530, Amit Kapila wrote: > 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. Yeah, well, this comes back to my original point that the upgrade of publisher nodes and subscriber nodes should be treated as two different problems or we're mixing apples and oranges (and a node could have both subscriber and publishers). While being able to support both is a must, it is going to be a two-step process at the end, with the subscribers done first and the publishers done after. That's also kind of the point that Julien makes in top message of this thread. I agree that docs are lacking in the proposed patch in terms of restrictions, assumptions and process flow, but taken in isolation the problem of the publishers is not something that this patch has to take care of. I'd certainly agree that it should mention, at least and if merged first, to be careful if upgrading the publishers as its slots are currently removed. -- Michael
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