On Thu, Jul 18, 2024 at 7:52 AM Zhijie Hou (Fujitsu) <houzj.f...@fujitsu.com> wrote: > > Attach the V5 patch set which changed the following: >
Tested v5-0001 patch, and it fails to detect the update_exists conflict for a setup where Pub has a non-partitioned table and Sub has the same table partitioned. Below is a testcase showcasing the issue: Setup: Pub: create table tab (a int not null, b int not null); alter table tab add constraint tab_pk primary key (a,b); Sub: create table tab (a int not null, b int not null) partition by range (b); alter table tab add constraint tab_pk primary key (a,b); CREATE TABLE tab_1 PARTITION OF tab FOR VALUES FROM (MINVALUE) TO (100); CREATE TABLE tab_2 PARTITION OF tab FOR VALUES FROM (101) TO (MAXVALUE); Test: Pub: insert into tab values (1,1); Sub: insert into tab values (2,1); Pub: update tab set a=2 where a=1; --> After this update on Pub, 'update_exists' is expected on Sub, but it fails to detect the conflict and logs the key violation error - ERROR: duplicate key value violates unique constraint "tab_1_pkey" DETAIL: Key (a, b)=(2, 1) already exists. Thanks, Nisha
