Horton

Re: pg_upgrade and logical replication

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
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-10-26T07:39:26Z
Lists: pgsql-hackers 
On Fri, Sep 29, 2023 at 05:32:52PM +0530, Amit Kapila wrote:
> Such a use case is possible to achieve even without this patch.
> Sawada-San has already given an alternative to slightly tweak the
> steps mentioned by Julien to achieve it. Also, there are other ways to
> achieve it by slightly changing the steps. OTOH, it will create a
> problem for normal logical replication set up after upgrade as
> discused.

So, now that 29d0a77fa6 has been applied to the tree, would it be time
to brush up what's been discussed on this thread for subscribers?  I'm
OK to spend time on it.
--
Michael

Commits

  1. pg_upgrade: Retrieve subscription count more efficiently.

  2. Fix random failure in 004_subscription.

  3. Fix 004_subscription.pl to allow its usage in --link mode.

  4. Allow upgrades to preserve the full subscription's state.

  5. Prevent startup of logical replication launcher during pg_upgrade