Re: row filtering for logical replication
От | Amit Kapila |
---|---|
Тема | Re: row filtering for logical replication |
Дата | |
Msg-id | CAA4eK1Je5kfXzUAtN3_=gqAiuFbBw2pwFUi72_nKxx8148TzJg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: row filtering for logical replication ("Euler Taveira" <euler@eulerto.com>) |
Ответы |
RE: row filtering for logical replication
|
Список | pgsql-hackers |
On Thu, Nov 25, 2021 at 7:39 PM Euler Taveira <euler@eulerto.com> wrote: > > On Thu, Nov 25, 2021, at 10:39 AM, houzj.fnst@fujitsu.com wrote: > > When researching and writing a top-up patch about this. > I found a possible issue which I'd like to confirm first. > > It's possible the table is published in two publications A and B, publication A > only publish "insert" , publication B publish "update". When UPDATE, both row > filter in A and B will be executed. Is this behavior expected? > > Good question. No. The code should check the action before combining the > multiple row filters. > Do you mean to say that we should give an error on Update/Delete if any of the publications contain table rowfilter that has columns that are not part of the primary key or replica identity? I think this is what Hou-san has implemented in his top-up patch and I also think this is the right behavior. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: