Re: Logical Replication not working for few Tables

Поиск
Список
Период
Сортировка
От Padmakumar Kadayaprth
Тема Re: Logical Replication not working for few Tables
Дата
Msg-id CAMjUpCr4c=+YFd=9cfqox6fY8dK2p_rDWFTwGixucYnZpFw9Zw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Logical Replication not working for few Tables  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: Logical Replication not working for few Tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
I created new tables and renamed the old tables like table_old  .
ex: Table Node to node_old and node_new to node
But still replication is not happening with the four tables .I added node_old to publication and subscribed to it .It worked fine .
What I am seeing is a table with a specific name  is not getting replicated . I am not sure why  .

On Tue, Nov 16, 2021 at 7:42 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
On Fri, Nov 12, 2021 at 8:06 PM Padmakumar Kadayaprth
<padmakumark26@gmail.com> wrote:
>
> Hi All,
>    I configured  logical replication some time back .Now except for 4 table replication is happening.Few weeks back replication got stopped because of some conflict and these 4 tables were part of that conflict.  Someone resolved the conflict but replication has not started for these four tables .I dropped these tables from publication and added it back and refreshed the subscription but still replication is not happening for these four .
>

The refresh won't do anything if the tables have already been
replicated previously.

> For testing I created a new table and added it to publication and refreshed subscription , that was sussues.
>
> Is there any system table where these 4 tables are marked as conflict and not to be replicated?
>

No.

> Why is replication not happening only to those four tables.is this a bug?
>

It is quite surprising that replication changes for a few tables is
getting skipped whereas it is successful for others. One guess is that
new changes are updates and deletes of rows that didn't exist in the
tables on subscriber-side, as one might have removed/changed those
rows while resolving conflicts. If that happens then we log the
message at DEBUG1 log level.

I think you can try to construct an independent test on the same lines
and resolve conflict in a similar way and then see what is happening?


--
With Regards,
Amit Kapila.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Дмитрий Иванов
Дата:
Сообщение: Re: pg_restore depending on user functions
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Logical Replication not working for few Tables