Re: Data is copied twice when specifying both child and parent table in publication
От | Amit Kapila |
---|---|
Тема | Re: Data is copied twice when specifying both child and parent table in publication |
Дата | |
Msg-id | CAA4eK1+RyFHLv1K+3qCdRmqEO0bz68Ga=Tzomvq4Rc40HnNO8A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Data is copied twice when specifying both child and parent table in publication (vignesh C <vignesh21@gmail.com>) |
Ответы |
Re: Data is copied twice when specifying both child and parent table in publication
|
Список | pgsql-hackers |
On Wed, Dec 8, 2021 at 11:30 AM vignesh C <vignesh21@gmail.com> wrote: > > On Wed, Dec 8, 2021 at 11:11 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Tue, Dec 7, 2021 at 5:53 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > On Fri, Dec 3, 2021 at 11:24 AM houzj.fnst@fujitsu.com > > > <houzj.fnst@fujitsu.com> wrote: > > > > > > > > > > 2) Any particular reason why the code and tests are backbranched but > > > not the document changes? > > > > > > > I am not sure whether we need the doc change or not as this is not a > > new feature and even if we need it as an improvement to docs, shall we > > consider backpatching it? I felt that code changes are required to fix > > a known issue so the case of backpatching it is clear. > > Thanks for the clarification, I got your point. I'm fine either way > regarding the documentation change. The rest of the patch looks good > to me. > Okay, I have also verified the code and test changes for all branches. I'll wait for a day to see if anybody else has any comments and then commit this. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: