Re: row filtering for logical replication
От | Amit Kapila |
---|---|
Тема | Re: row filtering for logical replication |
Дата | |
Msg-id | CAA4eK1LcAdzN8oMg+DNPgWrWvp8084CkLAhu86TvQixK=aK27Q@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: row filtering for logical replication ("tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>) |
Ответы |
RE: row filtering for logical replication
|
Список | pgsql-hackers |
On Thu, Jan 20, 2022 at 5:03 PM tanghy.fnst@fujitsu.com <tanghy.fnst@fujitsu.com> wrote: > > On Thu, Jan 20, 2022 9:13 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > Attach the V68 patch set which addressed the above comments and changes. > > The version patch also fix the error message mentioned by Greg[1] > > > > I saw a problem about this patch, which is related to Replica Identity check. > > For example: > -- publisher -- > create table tbl (a int); > create publication pub for table tbl where (a>10) with (publish='delete'); > insert into tbl values (1); > update tbl set a=a+1; > > postgres=# update tbl set a=a+1; > ERROR: cannot update table "tbl" > DETAIL: Column "a" used in the publication WHERE expression is not part of the replica identity. > > I think it shouldn't report the error because the publication didn't publish UPDATES. > Right, I also don't see any reason why an error should be thrown in this case. The problem here is that the patch doesn't have any correspondence between the pubaction and RI column validation for a particular publication. I think we need to do that and cache that information unless the publication publishes both updates and deletes in which case it is okay to directly return invalid column in row filter as we are doing now. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: