Re: pg_upgrade and logical replication

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade and logical replication
Date: 2023-10-26 07:39:26
Message-ID: ZToXrkW1wAfVWOrk@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema 2023-10-26 08:00:53 Re: libpq async connection and multiple hosts
Previous Message Michael Paquier 2023-10-26 07:31:19 Re: Is this a problem in GenericXLogFinish()?