Re: pg_upgrade and publication/subscription problem

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and publication/subscription problem
Date: 2021-11-29 03:38:19
Message-ID: CAA4eK1KkWLJX7xUVO8Ae0Ljv-Z17B77sNuFOJMTN36uqnXJTpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 26, 2021 at 5:47 PM Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
>>
>> So, in short, I think what we need to solve is to get the data from
>> new tables and newly performed writes on old tables. I could think of
>> the following two approaches:
>>
>> Approach-1:
>> 1. Drop subscription and Truncate all tables corresponding to subscription.
>>
>> 2. Create a new subscription for the publication.
>
> If I drop subscription it will drop WAL ou publication side and I lost all changed data between the starting of pg_upgrade process and now.
>

On thinking about this point again, it is not clear to me why that
would matter for this particular use case? Basically, when you create
a new subscription, it should copy the entire existing data from the
table directly and then will decode changes from WAL. So, I think in
your case all the changes between pg_upgrade and now should be
directly copied from tables, so probably older WAL won't be required.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-11-29 03:43:34 Re: Skipping logical replication transactions on subscriber side
Previous Message Masahiko Sawada 2021-11-29 03:38:08 Re: parallel vacuum comments