Re: Handle infinite recursion in logical replication setup
От | vignesh C |
---|---|
Тема | Re: Handle infinite recursion in logical replication setup |
Дата | |
Msg-id | CALDaNm3sEkLDsgSLi_1Z6jk+CQ3JzQNc6vPtgCLpqn0YCM2H0g@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Handle infinite recursion in logical replication setup ("kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>) |
Ответы |
Re: Handle infinite recursion in logical replication setup
|
Список | pgsql-hackers |
On Tue, Mar 15, 2022 at 9:55 AM kuroda.hayato@fujitsu.com <kuroda.hayato@fujitsu.com> wrote: > > Dear Vignesh, > > > Thanks for kind explanation. > > I read above and your doc in 0002, and I put some comments. > > I forgot a comment about 0002 doc. > > 5. create_subscription.sgml - about your example > > Three possibilities were listed in the doc, > but I was not sure about b) case. > In the situation Node1 and Node2 have already become multi-master, > and data has already synced at that time. > If so, how do we realize that "there is data present only in one Node"? > Case a) and c) seem reasonable. Your point is valid, modified. The changes for the same are available int the v5 patch available at [1]. [1] - https://www.postgresql.org/message-id/CALDaNm3wCf0YcvVo%2BgHMGpupk9K6WKJxCyLUvhPC2GkPKRZUWA%40mail.gmail.com Regards, Vignesh
В списке pgsql-hackers по дате отправления: