Re: pg_upgrade and publication/subscription problem - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pg_upgrade and publication/subscription problem
Date
Msg-id CAA4eK1KVfSzrw_48e8EgSkiTUk4O9dHdoJkV-667hC3hE5uRJQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade and publication/subscription problem  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: pg_upgrade and publication/subscription problem
List pgsql-hackers
On Mon, Nov 29, 2021 at 5:04 PM Marcos Pegoraro <marcos@f10.com.br> wrote:
>>
>> 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.
>
>
> Maybe you did not understand
>

Yeah, because some information like trigger functions was not there in
your previous emails.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: row filtering for logical replication
Next
From: Bharath Rupireddy
Date:
Subject: Re: Synchronizing slots from primary to standby