2026-05-06 14:58:46.188 UTC postmaster[55845] LOG: starting PostgreSQL 19devel on aarch64-darwin, compiled by clang-17.0.0, 64-bit 2026-05-06 14:58:46.188 UTC postmaster[55845] LOG: listening on Unix socket "/var/folders/hm/d7rr9ds96qx995ns72ry9g4m0000gn/T/YqMuJvZCLw/.s.PGSQL.20285" 2026-05-06 14:58:46.202 UTC startup[55859] LOG: database system was shut down at 2026-05-06 14:49:11 UTC 2026-05-06 14:58:46.211 UTC postmaster[55845] LOG: database system is ready to accept connections 2026-05-06 14:58:46.470 UTC client backend[55900] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:46.478 UTC client backend[55900] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:46.478 UTC client backend[55900] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:46.545 UTC client backend[55900] 035_conflicts.pl LOG: connection ready: setup total=77.869 ms, fork=2.631 ms, authentication=5.582 ms 2026-05-06 14:58:46.546 UTC client backend[55900] 035_conflicts.pl LOG: statement: CREATE TABLE conf_tab (a int PRIMARY key, b int UNIQUE, c int UNIQUE); 2026-05-06 14:58:46.552 UTC client backend[55900] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.082 user=admin database=postgres host=[local] 2026-05-06 14:58:46.590 UTC client backend[55913] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:46.591 UTC client backend[55913] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:46.591 UTC client backend[55913] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:46.593 UTC client backend[55913] 035_conflicts.pl LOG: connection ready: setup total=4.877 ms, fork=1.972 ms, authentication=0.366 ms 2026-05-06 14:58:46.593 UTC client backend[55913] 035_conflicts.pl LOG: statement: CREATE TABLE conf_tab_2 (a int PRIMARY KEY, b int, c int, unique(a,b)) PARTITION BY RANGE (a); 2026-05-06 14:58:46.597 UTC client backend[55913] 035_conflicts.pl LOG: statement: CREATE TABLE conf_tab_2_p1 PARTITION OF conf_tab_2 FOR VALUES FROM (MINVALUE) TO (100); 2026-05-06 14:58:46.599 UTC client backend[55913] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.009 user=admin database=postgres host=[local] 2026-05-06 14:58:46.697 UTC client backend[55927] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:46.698 UTC client backend[55927] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:46.698 UTC client backend[55927] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:46.699 UTC client backend[55927] 035_conflicts.pl LOG: connection ready: setup total=4.759 ms, fork=1.990 ms, authentication=0.382 ms 2026-05-06 14:58:46.700 UTC client backend[55927] 035_conflicts.pl LOG: statement: CREATE SUBSCRIPTION sub_tab CONNECTION 'port=20284 host=/var/folders/hm/d7rr9ds96qx995ns72ry9g4m0000gn/T/YqMuJvZCLw dbname=postgres application_name=sub_tab' PUBLICATION pub_tab WITH (conflict_log_destination=all) 2026-05-06 14:58:46.731 UTC client backend[55927] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.034 user=admin database=postgres host=[local] 2026-05-06 14:58:46.735 UTC logical replication apply worker[55933] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:46.758 UTC logical replication tablesync worker[55936] LOG: logical replication table synchronization worker for subscription "sub_tab", table "conf_tab" has started 2026-05-06 14:58:46.775 UTC logical replication tablesync worker[55938] LOG: logical replication table synchronization worker for subscription "sub_tab", table "conf_tab_2" has started 2026-05-06 14:58:46.782 UTC client backend[55941] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:46.783 UTC client backend[55941] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:46.783 UTC client backend[55941] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:46.784 UTC client backend[55941] 035_conflicts.pl LOG: connection ready: setup total=5.211 ms, fork=2.924 ms, authentication=0.168 ms 2026-05-06 14:58:46.785 UTC client backend[55941] 035_conflicts.pl LOG: statement: SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r', 's'); 2026-05-06 14:58:46.789 UTC client backend[55941] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.007 user=admin database=postgres host=[local] 2026-05-06 14:58:46.792 UTC logical replication tablesync worker[55936] LOG: logical replication table synchronization worker for subscription "sub_tab", table "conf_tab" has finished 2026-05-06 14:58:46.816 UTC logical replication tablesync worker[55938] LOG: logical replication table synchronization worker for subscription "sub_tab", table "conf_tab_2" has finished 2026-05-06 14:58:46.931 UTC client backend[55960] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:46.931 UTC client backend[55960] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:46.931 UTC client backend[55960] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:46.932 UTC client backend[55960] 035_conflicts.pl LOG: connection ready: setup total=3.899 ms, fork=1.744 ms, authentication=0.180 ms 2026-05-06 14:58:46.933 UTC client backend[55960] 035_conflicts.pl LOG: statement: SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r', 's'); 2026-05-06 14:58:46.935 UTC client backend[55960] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:47.196 UTC client backend[56009] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.197 UTC client backend[56009] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.197 UTC client backend[56009] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.198 UTC client backend[56009] 035_conflicts.pl LOG: connection ready: setup total=2.348 ms, fork=0.626 ms, authentication=0.149 ms 2026-05-06 14:58:47.198 UTC client backend[56009] 035_conflicts.pl LOG: statement: INSERT INTO conf_tab VALUES (2,2,2), (3,3,3), (4,4,4); 2026-05-06 14:58:47.198 UTC client backend[56009] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:47.239 UTC logical replication apply worker[55933] ERROR: conflict detected on relation "public.conf_tab": conflict=multiple_unique_conflicts 2026-05-06 14:58:47.239 UTC logical replication apply worker[55933] DETAIL: Could not apply remote change: remote row (2, 3, 4). Key already exists in unique index "conf_tab_pkey", modified in transaction 708: key (a)=(2), local row (2, 2, 2). Key already exists in unique index "conf_tab_b_key", modified in transaction 708: key (b)=(3), local row (3, 3, 3). Key already exists in unique index "conf_tab_c_key", modified in transaction 708: key (c)=(4), local row (4, 4, 4). 2026-05-06 14:58:47.239 UTC logical replication apply worker[55933] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab" in transaction 697, finished at 0/017DACF8 2026-05-06 14:58:47.243 UTC postmaster[55845] LOG: background worker "logical replication apply worker" (PID 55933) exited with exit code 1 2026-05-06 14:58:47.247 UTC logical replication apply worker[56015] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:47.258 UTC logical replication apply worker[56015] ERROR: conflict detected on relation "public.conf_tab": conflict=multiple_unique_conflicts 2026-05-06 14:58:47.258 UTC logical replication apply worker[56015] DETAIL: Could not apply remote change: remote row (2, 3, 4). Key already exists in unique index "conf_tab_pkey", modified in transaction 708: key (a)=(2), local row (2, 2, 2). Key already exists in unique index "conf_tab_b_key", modified in transaction 708: key (b)=(3), local row (3, 3, 3). Key already exists in unique index "conf_tab_c_key", modified in transaction 708: key (c)=(4), local row (4, 4, 4). 2026-05-06 14:58:47.258 UTC logical replication apply worker[56015] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab" in transaction 697, finished at 0/017DACF8 2026-05-06 14:58:47.260 UTC postmaster[55845] LOG: background worker "logical replication apply worker" (PID 56015) exited with exit code 1 2026-05-06 14:58:47.389 UTC client backend[56040] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.390 UTC client backend[56040] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.390 UTC client backend[56040] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.391 UTC client backend[56040] 035_conflicts.pl LOG: connection ready: setup total=4.681 ms, fork=2.735 ms, authentication=0.144 ms 2026-05-06 14:58:47.391 UTC client backend[56040] 035_conflicts.pl LOG: statement: SELECT oid FROM pg_subscription WHERE subname = 'sub_tab'; 2026-05-06 14:58:47.394 UTC client backend[56040] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:47.450 UTC client backend[56051] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.450 UTC client backend[56051] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.450 UTC client backend[56051] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.451 UTC client backend[56051] 035_conflicts.pl LOG: connection ready: setup total=2.674 ms, fork=1.548 ms, authentication=0.113 ms 2026-05-06 14:58:47.451 UTC client backend[56051] 035_conflicts.pl LOG: statement: SELECT count(*) > 0 FROM pg_conflict.pg_conflict_log_16410; 2026-05-06 14:58:47.453 UTC client backend[56051] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:47.492 UTC client backend[56058] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.492 UTC client backend[56058] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.492 UTC client backend[56058] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.493 UTC client backend[56058] 035_conflicts.pl LOG: connection ready: setup total=1.767 ms, fork=0.549 ms, authentication=0.116 ms 2026-05-06 14:58:47.493 UTC client backend[56058] 035_conflicts.pl LOG: statement: SELECT count(*) >= 1 FROM pg_conflict.pg_conflict_log_16410 WHERE conflict_type = 'multiple_unique_conflicts'; 2026-05-06 14:58:47.494 UTC client backend[56058] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:47.519 UTC client backend[56064] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.520 UTC client backend[56064] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.520 UTC client backend[56064] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.521 UTC client backend[56064] 035_conflicts.pl LOG: connection ready: setup total=3.279 ms, fork=0.822 ms, authentication=0.263 ms 2026-05-06 14:58:47.521 UTC client backend[56064] 035_conflicts.pl LOG: statement: SELECT local_conflicts FROM pg_conflict.pg_conflict_log_16410; 2026-05-06 14:58:47.522 UTC client backend[56064] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:47.557 UTC client backend[56073] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.558 UTC client backend[56073] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.558 UTC client backend[56073] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.559 UTC client backend[56073] 035_conflicts.pl LOG: connection ready: setup total=4.493 ms, fork=2.290 ms, authentication=0.201 ms 2026-05-06 14:58:47.566 UTC client backend[56073] 035_conflicts.pl LOG: statement: TRUNCATE conf_tab; 2026-05-06 14:58:47.572 UTC client backend[56073] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.014 user=admin database=postgres host=[local] 2026-05-06 14:58:47.640 UTC client backend[56083] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.640 UTC client backend[56083] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.640 UTC client backend[56083] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.641 UTC client backend[56083] 035_conflicts.pl LOG: connection ready: setup total=4.325 ms, fork=3.007 ms, authentication=0.145 ms 2026-05-06 14:58:47.641 UTC client backend[56083] 035_conflicts.pl LOG: statement: DELETE FROM pg_conflict.pg_conflict_log_16410 2026-05-06 14:58:47.642 UTC client backend[56083] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:47.716 UTC client backend[56099] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.716 UTC client backend[56099] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.716 UTC client backend[56099] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.717 UTC client backend[56099] 035_conflicts.pl LOG: connection ready: setup total=3.183 ms, fork=1.645 ms, authentication=0.095 ms 2026-05-06 14:58:47.717 UTC client backend[56099] 035_conflicts.pl LOG: statement: INSERT INTO conf_tab VALUES (6,6,6), (7,7,7), (8,8,8); 2026-05-06 14:58:47.718 UTC client backend[56099] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:47.748 UTC logical replication apply worker[56105] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:47.757 UTC logical replication apply worker[56105] ERROR: conflict detected on relation "public.conf_tab": conflict=multiple_unique_conflicts 2026-05-06 14:58:47.757 UTC logical replication apply worker[56105] DETAIL: Could not apply remote change: remote row (6, 7, 8), replica identity (a)=(5). Key already exists in unique index "conf_tab_pkey", modified in transaction 715: key (a)=(6), local row (6, 6, 6). Key already exists in unique index "conf_tab_b_key", modified in transaction 715: key (b)=(7), local row (7, 7, 7). Key already exists in unique index "conf_tab_c_key", modified in transaction 715: key (c)=(8), local row (8, 8, 8). 2026-05-06 14:58:47.757 UTC logical replication apply worker[56105] CONTEXT: processing remote data for replication origin "pg_16410" during message type "UPDATE" for replication target relation "public.conf_tab" in transaction 699, finished at 0/017DAF78 2026-05-06 14:58:47.759 UTC postmaster[55845] LOG: background worker "logical replication apply worker" (PID 56105) exited with exit code 1 2026-05-06 14:58:47.796 UTC client backend[56118] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.796 UTC client backend[56118] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.796 UTC client backend[56118] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.798 UTC client backend[56118] 035_conflicts.pl LOG: connection ready: setup total=4.474 ms, fork=2.317 ms, authentication=0.263 ms 2026-05-06 14:58:47.798 UTC client backend[56118] 035_conflicts.pl LOG: statement: SELECT count(*) > 0 FROM pg_conflict.pg_conflict_log_16410; 2026-05-06 14:58:47.799 UTC client backend[56118] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:47.827 UTC client backend[56128] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.828 UTC client backend[56128] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.828 UTC client backend[56128] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.828 UTC client backend[56128] 035_conflicts.pl LOG: connection ready: setup total=3.111 ms, fork=1.673 ms, authentication=0.149 ms 2026-05-06 14:58:47.829 UTC client backend[56128] 035_conflicts.pl LOG: statement: SELECT count(*) >= 1 FROM pg_conflict.pg_conflict_log_16410 WHERE conflict_type = 'multiple_unique_conflicts'; 2026-05-06 14:58:47.831 UTC client backend[56128] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:47.876 UTC client backend[56136] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.876 UTC client backend[56136] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.876 UTC client backend[56136] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.878 UTC client backend[56136] 035_conflicts.pl LOG: connection ready: setup total=2.780 ms, fork=0.736 ms, authentication=0.092 ms 2026-05-06 14:58:47.878 UTC client backend[56136] 035_conflicts.pl LOG: statement: SELECT local_conflicts FROM pg_conflict.pg_conflict_log_16410; 2026-05-06 14:58:47.879 UTC client backend[56136] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:47.903 UTC client backend[56143] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.904 UTC client backend[56143] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.904 UTC client backend[56143] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.904 UTC client backend[56143] 035_conflicts.pl LOG: connection ready: setup total=1.642 ms, fork=0.510 ms, authentication=0.106 ms 2026-05-06 14:58:47.905 UTC client backend[56143] 035_conflicts.pl LOG: statement: TRUNCATE conf_tab; 2026-05-06 14:58:47.906 UTC client backend[56143] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:47.925 UTC client backend[56151] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:47.925 UTC client backend[56151] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:47.925 UTC client backend[56151] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:47.926 UTC client backend[56151] 035_conflicts.pl LOG: connection ready: setup total=1.531 ms, fork=0.446 ms, authentication=0.094 ms 2026-05-06 14:58:47.926 UTC client backend[56151] 035_conflicts.pl LOG: statement: INSERT INTO conf_tab_2 VALUES (55,2,3); 2026-05-06 14:58:47.930 UTC client backend[56151] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:48.253 UTC logical replication apply worker[56205] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:48.258 UTC logical replication apply worker[56205] LOG: conflict detected on relation "public.conf_tab": conflict=update_missing 2026-05-06 14:58:48.258 UTC logical replication apply worker[56205] DETAIL: Could not find the row to be updated: remote row (6, 7, 8), replica identity (a)=(5). 2026-05-06 14:58:48.258 UTC logical replication apply worker[56205] CONTEXT: processing remote data for replication origin "pg_16410" during message type "UPDATE" for replication target relation "public.conf_tab" in transaction 699, finished at 0/017DAF78 2026-05-06 14:58:48.259 UTC logical replication apply worker[56205] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:48.259 UTC logical replication apply worker[56205] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:48.259 UTC logical replication apply worker[56205] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:48.261 UTC postmaster[55845] LOG: background worker "logical replication apply worker" (PID 56205) exited with exit code 1 2026-05-06 14:58:48.574 UTC postmaster[55845] LOG: received fast shutdown request 2026-05-06 14:58:48.575 UTC postmaster[55845] LOG: aborting any active transactions 2026-05-06 14:58:48.582 UTC postmaster[55845] LOG: background worker "logical replication launcher" (PID 55863) exited with exit code 1 2026-05-06 14:58:48.582 UTC checkpointer[55857] LOG: shutting down 2026-05-06 14:58:48.582 UTC checkpointer[55857] LOG: checkpoint starting: shutdown fast 2026-05-06 14:58:48.586 UTC checkpointer[55857] LOG: checkpoint complete: shutdown fast: wrote 22 buffers (17.2%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.005 s; sync files=0, longest=0.000 s, average=0.000 s; distance=277 kB, estimate=277 kB; lsn=0/017E7C48, redo lsn=0/017E7C48 2026-05-06 14:58:48.592 UTC postmaster[55845] LOG: database system is shut down 2026-05-06 14:58:48.739 UTC postmaster[56273] LOG: starting PostgreSQL 19devel on aarch64-darwin, compiled by clang-17.0.0, 64-bit 2026-05-06 14:58:48.739 UTC postmaster[56273] LOG: listening on Unix socket "/var/folders/hm/d7rr9ds96qx995ns72ry9g4m0000gn/T/YqMuJvZCLw/.s.PGSQL.20285" 2026-05-06 14:58:48.748 UTC startup[56283] LOG: database system was shut down at 2026-05-06 14:58:48 UTC 2026-05-06 14:58:48.749 UTC startup[56283] LOG: recovered replication state of node 1 to 0/017DAFA8 2026-05-06 14:58:48.750 UTC postmaster[56273] LOG: database system is ready to accept connections 2026-05-06 14:58:48.765 UTC logical replication apply worker[56288] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:48.803 UTC logical replication apply worker[56288] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:48.803 UTC logical replication apply worker[56288] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:48.803 UTC logical replication apply worker[56288] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:48.813 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56288) exited with exit code 1 2026-05-06 14:58:48.889 UTC client backend[56305] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:48.890 UTC client backend[56305] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:48.890 UTC client backend[56305] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:48.891 UTC client backend[56305] 035_conflicts.pl LOG: connection ready: setup total=2.840 ms, fork=0.641 ms, authentication=0.269 ms 2026-05-06 14:58:48.891 UTC client backend[56305] 035_conflicts.pl LOG: statement: CREATE TABLE tab (a int PRIMARY KEY, b int) 2026-05-06 14:58:48.894 UTC client backend[56305] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.005 user=admin database=postgres host=[local] 2026-05-06 14:58:48.967 UTC client backend[56314] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:48.968 UTC client backend[56314] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:48.968 UTC client backend[56314] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:48.970 UTC client backend[56314] 035_conflicts.pl LOG: connection ready: setup total=4.959 ms, fork=1.694 ms, authentication=0.348 ms 2026-05-06 14:58:48.970 UTC client backend[56314] 035_conflicts.pl LOG: statement: CREATE SUBSCRIPTION tap_sub_b_a CONNECTION 'port=20284 host=/var/folders/hm/d7rr9ds96qx995ns72ry9g4m0000gn/T/YqMuJvZCLw dbname=postgres application_name=tap_sub_b_a' PUBLICATION tap_pub_A WITH (origin = none, retain_dead_tuples = true) 2026-05-06 14:58:49.046 UTC logical replication launcher[56287] LOG: creating replication conflict detection slot 2026-05-06 14:58:49.047 UTC client backend[56314] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.080 user=admin database=postgres host=[local] 2026-05-06 14:58:49.056 UTC logical replication apply worker[56328] LOG: logical replication apply worker for subscription "tap_sub_b_a" has started 2026-05-06 14:58:49.079 UTC client backend[56332] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.080 UTC client backend[56332] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.080 UTC client backend[56332] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.080 UTC logical replication tablesync worker[56330] LOG: logical replication table synchronization worker for subscription "tap_sub_b_a", table "tab" has started 2026-05-06 14:58:49.082 UTC client backend[56332] 035_conflicts.pl LOG: connection ready: setup total=3.890 ms, fork=0.725 ms, authentication=0.349 ms 2026-05-06 14:58:49.082 UTC client backend[56332] 035_conflicts.pl LOG: statement: CREATE PUBLICATION tap_pub_B FOR TABLE tab 2026-05-06 14:58:49.084 UTC client backend[56332] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:49.105 UTC logical replication tablesync worker[56330] LOG: logical replication table synchronization worker for subscription "tap_sub_b_a", table "tab" has finished 2026-05-06 14:58:49.170 UTC client backend[56344] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.171 UTC walsender[56344] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.171 UTC walsender[56344] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.172 UTC walsender[56344] tap_sub_a_b LOG: connection ready: setup total=4.836 ms, fork=3.131 ms, authentication=0.149 ms 2026-05-06 14:58:49.172 UTC walsender[56344] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.174 UTC walsender[56344] tap_sub_a_b LOG: statement: SELECT t.pubname FROM pg_catalog.pg_publication t WHERE t.pubname IN ('tap_pub_b') 2026-05-06 14:58:49.178 UTC walsender[56344] tap_sub_a_b LOG: statement: SELECT DISTINCT n.nspname, c.relname, c.relkind, gpt.attrs FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace JOIN ( SELECT (pg_get_publication_tables(VARIADIC array_agg(pubname::text))).* FROM pg_publication WHERE pubname IN ( 'tap_pub_b' )) AS gpt ON gpt.relid = c.oid UNION ALL SELECT DISTINCT s.schemaname, s.sequencename, 'S'::"char" AS relkind, NULL::int2vector AS attrs FROM pg_catalog.pg_publication_sequences s WHERE s.pubname IN ( 'tap_pub_b' ) 2026-05-06 14:58:49.188 UTC walsender[56344] tap_sub_a_b LOG: received replication command: CREATE_REPLICATION_SLOT "tap_sub_a_b" LOGICAL pgoutput (SNAPSHOT 'nothing') 2026-05-06 14:58:49.188 UTC walsender[56344] tap_sub_a_b STATEMENT: CREATE_REPLICATION_SLOT "tap_sub_a_b" LOGICAL pgoutput (SNAPSHOT 'nothing') 2026-05-06 14:58:49.217 UTC walsender[56344] tap_sub_a_b LOG: logical decoding found consistent point at 0/0180DD70 2026-05-06 14:58:49.217 UTC walsender[56344] tap_sub_a_b DETAIL: There are no running transactions. 2026-05-06 14:58:49.217 UTC walsender[56344] tap_sub_a_b STATEMENT: CREATE_REPLICATION_SLOT "tap_sub_a_b" LOGICAL pgoutput (SNAPSHOT 'nothing') 2026-05-06 14:58:49.218 UTC walsender[56344] tap_sub_a_b LOG: released logical replication slot "tap_sub_a_b" 2026-05-06 14:58:49.218 UTC walsender[56344] tap_sub_a_b STATEMENT: CREATE_REPLICATION_SLOT "tap_sub_a_b" LOGICAL pgoutput (SNAPSHOT 'nothing') 2026-05-06 14:58:49.218 UTC walsender[56344] tap_sub_a_b LOG: disconnection: session time: 0:00:00.048 user=admin database=postgres host=[local] 2026-05-06 14:58:49.251 UTC client backend[56352] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.252 UTC walsender[56352] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.252 UTC walsender[56352] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.255 UTC walsender[56352] tap_sub_a_b LOG: connection ready: setup total=6.411 ms, fork=2.295 ms, authentication=0.467 ms 2026-05-06 14:58:49.255 UTC walsender[56352] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b LOG: received replication command: IDENTIFY_SYSTEM 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b STATEMENT: IDENTIFY_SYSTEM 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b LOG: received replication command: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b LOG: acquired logical replication slot "tap_sub_a_b" 2026-05-06 14:58:49.256 UTC walsender[56352] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b LOG: starting logical decoding for slot "tap_sub_a_b" 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b DETAIL: Streaming transactions committing after 0/0180DDA8, reading WAL from 0/0180DD70. 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b LOG: logical decoding found consistent point at 0/0180DD70 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b DETAIL: There are no running transactions. 2026-05-06 14:58:49.258 UTC walsender[56352] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.260 UTC logical replication apply worker[56354] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:49.271 UTC logical replication apply worker[56354] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:49.271 UTC logical replication apply worker[56354] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:49.271 UTC logical replication apply worker[56354] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:49.273 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56354) exited with exit code 1 2026-05-06 14:58:49.321 UTC client backend[56365] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.321 UTC client backend[56365] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.321 UTC client backend[56365] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.323 UTC client backend[56365] 035_conflicts.pl LOG: connection ready: setup total=5.281 ms, fork=2.809 ms, authentication=0.208 ms 2026-05-06 14:58:49.323 UTC client backend[56365] 035_conflicts.pl LOG: statement: SELECT pg_is_in_recovery() 2026-05-06 14:58:49.325 UTC client backend[56365] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:49.356 UTC client backend[56369] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.356 UTC client backend[56369] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.357 UTC client backend[56369] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.358 UTC client backend[56369] 035_conflicts.pl LOG: connection ready: setup total=4.661 ms, fork=2.244 ms, authentication=0.230 ms 2026-05-06 14:58:49.358 UTC client backend[56369] 035_conflicts.pl LOG: statement: SELECT pg_current_wal_lsn() 2026-05-06 14:58:49.360 UTC client backend[56369] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.004 user=admin database=postgres host=[local] 2026-05-06 14:58:49.396 UTC client backend[56376] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.396 UTC client backend[56376] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.396 UTC client backend[56376] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.397 UTC client backend[56376] 035_conflicts.pl LOG: connection ready: setup total=1.912 ms, fork=0.622 ms, authentication=0.095 ms 2026-05-06 14:58:49.397 UTC client backend[56376] 035_conflicts.pl LOG: statement: SELECT '0/0180DDA8' <= replay_lsn AND state = 'streaming' FROM pg_catalog.pg_stat_replication WHERE application_name IN ('tap_sub_a_b', 'walreceiver') 2026-05-06 14:58:49.401 UTC client backend[56376] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.005 user=admin database=postgres host=[local] 2026-05-06 14:58:49.435 UTC client backend[56383] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.435 UTC client backend[56383] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.435 UTC client backend[56383] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.436 UTC client backend[56383] 035_conflicts.pl LOG: connection ready: setup total=3.132 ms, fork=1.612 ms, authentication=0.135 ms 2026-05-06 14:58:49.436 UTC client backend[56383] 035_conflicts.pl LOG: statement: SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r', 's'); 2026-05-06 14:58:49.438 UTC client backend[56383] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:49.632 UTC client backend[56413] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.633 UTC client backend[56413] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.633 UTC client backend[56413] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:49.635 UTC client backend[56413] 035_conflicts.pl LOG: connection ready: setup total=4.720 ms, fork=2.320 ms, authentication=0.183 ms 2026-05-06 14:58:49.635 UTC client backend[56413] 035_conflicts.pl LOG: statement: SELECT xmin IS NOT NULL from pg_replication_slots WHERE slot_name = 'pg_conflict_detection' 2026-05-06 14:58:49.640 UTC client backend[56413] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.007 user=admin database=postgres host=[local] 2026-05-06 14:58:49.698 UTC walsender[56352] tap_sub_a_b LOG: released logical replication slot "tap_sub_a_b" 2026-05-06 14:58:49.699 UTC walsender[56352] tap_sub_a_b LOG: disconnection: session time: 0:00:00.447 user=admin database=postgres host=[local] 2026-05-06 14:58:49.759 UTC logical replication apply worker[56437] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:49.772 UTC logical replication apply worker[56437] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:49.772 UTC logical replication apply worker[56437] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:49.772 UTC logical replication apply worker[56437] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:49.775 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56437) exited with exit code 1 2026-05-06 14:58:49.779 UTC client backend[56444] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.780 UTC walsender[56444] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.780 UTC walsender[56444] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.781 UTC walsender[56444] tap_sub_a_b LOG: connection ready: setup total=3.202 ms, fork=1.554 ms, authentication=0.168 ms 2026-05-06 14:58:49.782 UTC walsender[56444] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.782 UTC walsender[56444] tap_sub_a_b LOG: statement: SELECT pg_is_in_recovery() 2026-05-06 14:58:49.783 UTC walsender[56444] tap_sub_a_b LOG: disconnection: session time: 0:00:00.003 user=admin database=postgres host=[local] 2026-05-06 14:58:49.906 UTC client backend[56464] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.907 UTC walsender[56464] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.907 UTC walsender[56464] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.908 UTC walsender[56464] tap_sub_a_b LOG: connection ready: setup total=3.956 ms, fork=2.083 ms, authentication=0.133 ms 2026-05-06 14:58:49.908 UTC walsender[56464] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.908 UTC walsender[56464] tap_sub_a_b LOG: statement: SELECT pg_is_in_recovery() 2026-05-06 14:58:49.908 UTC walsender[56464] tap_sub_a_b LOG: disconnection: session time: 0:00:00.002 user=admin database=postgres host=[local] 2026-05-06 14:58:49.919 UTC client backend[56470] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.920 UTC walsender[56470] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.920 UTC walsender[56470] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.920 UTC walsender[56470] tap_sub_a_b LOG: connection ready: setup total=3.245 ms, fork=1.978 ms, authentication=0.108 ms 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b LOG: received replication command: IDENTIFY_SYSTEM 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b STATEMENT: IDENTIFY_SYSTEM 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b LOG: received replication command: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b LOG: acquired logical replication slot "tap_sub_a_b" 2026-05-06 14:58:49.921 UTC walsender[56470] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b LOG: starting logical decoding for slot "tap_sub_a_b" 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b DETAIL: Streaming transactions committing after 0/0180E098, reading WAL from 0/0180DD70. 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b LOG: logical decoding found consistent point at 0/0180DD70 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b DETAIL: There are no running transactions. 2026-05-06 14:58:49.922 UTC walsender[56470] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:49.984 UTC client backend[56480] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:49.985 UTC walsender[56480] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:49.985 UTC walsender[56480] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:49.985 UTC walsender[56480] tap_sub_a_b LOG: connection ready: setup total=1.666 ms, fork=0.375 ms, authentication=0.108 ms 2026-05-06 14:58:49.986 UTC walsender[56480] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:49.986 UTC walsender[56480] tap_sub_a_b LOG: statement: SELECT pg_is_in_recovery() 2026-05-06 14:58:49.986 UTC walsender[56480] tap_sub_a_b LOG: statement: SELECT DISTINCT P.pubname AS pubname FROM pg_publication P, LATERAL pg_get_publication_tables(P.pubname) GPT JOIN pg_subscription_rel PS ON (GPT.relid = PS.srrelid OR GPT.relid IN (SELECT relid FROM pg_partition_ancestors(PS.srrelid) UNION SELECT relid FROM pg_partition_tree(PS.srrelid))), pg_class C JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE C.oid = GPT.relid AND P.pubname IN ('tap_pub_b') 2026-05-06 14:58:49.991 UTC walsender[56480] tap_sub_a_b LOG: disconnection: session time: 0:00:00.007 user=admin database=postgres host=[local] 2026-05-06 14:58:49.995 UTC walsender[56470] tap_sub_a_b LOG: released logical replication slot "tap_sub_a_b" 2026-05-06 14:58:49.995 UTC walsender[56470] tap_sub_a_b LOG: disconnection: session time: 0:00:00.076 user=admin database=postgres host=[local] 2026-05-06 14:58:50.010 UTC client backend[56488] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:50.011 UTC walsender[56488] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:50.011 UTC walsender[56488] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:50.012 UTC walsender[56488] tap_sub_a_b LOG: connection ready: setup total=3.249 ms, fork=1.848 ms, authentication=0.162 ms 2026-05-06 14:58:50.012 UTC walsender[56488] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b LOG: received replication command: IDENTIFY_SYSTEM 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b STATEMENT: IDENTIFY_SYSTEM 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b LOG: received replication command: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b LOG: acquired logical replication slot "tap_sub_a_b" 2026-05-06 14:58:50.013 UTC walsender[56488] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b LOG: starting logical decoding for slot "tap_sub_a_b" 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b DETAIL: Streaming transactions committing after 0/0180E370, reading WAL from 0/0180DD70. 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b LOG: logical decoding found consistent point at 0/0180DD70 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b DETAIL: There are no running transactions. 2026-05-06 14:58:50.014 UTC walsender[56488] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.035 UTC walsender[56488] tap_sub_a_b LOG: released logical replication slot "tap_sub_a_b" 2026-05-06 14:58:50.035 UTC walsender[56488] tap_sub_a_b LOG: disconnection: session time: 0:00:00.024 user=admin database=postgres host=[local] 2026-05-06 14:58:50.054 UTC client backend[56498] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:50.054 UTC walsender[56498] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:50.054 UTC walsender[56498] [unknown] LOG: replication connection authorized: user=admin application_name=tap_sub_a_b 2026-05-06 14:58:50.055 UTC walsender[56498] tap_sub_a_b LOG: connection ready: setup total=9.350 ms, fork=7.765 ms, authentication=0.198 ms 2026-05-06 14:58:50.057 UTC walsender[56498] tap_sub_a_b LOG: statement: SELECT pg_catalog.set_config('search_path', '', false); 2026-05-06 14:58:50.059 UTC walsender[56498] tap_sub_a_b LOG: received replication command: IDENTIFY_SYSTEM 2026-05-06 14:58:50.059 UTC walsender[56498] tap_sub_a_b STATEMENT: IDENTIFY_SYSTEM 2026-05-06 14:58:50.063 UTC walsender[56498] tap_sub_a_b LOG: received replication command: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.063 UTC walsender[56498] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.063 UTC walsender[56498] tap_sub_a_b LOG: acquired logical replication slot "tap_sub_a_b" 2026-05-06 14:58:50.063 UTC walsender[56498] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b LOG: starting logical decoding for slot "tap_sub_a_b" 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b DETAIL: Streaming transactions committing after 0/0180E370, reading WAL from 0/0180DD70. 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b LOG: logical decoding found consistent point at 0/0180DD70 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b DETAIL: There are no running transactions. 2026-05-06 14:58:50.064 UTC walsender[56498] tap_sub_a_b STATEMENT: START_REPLICATION SLOT "tap_sub_a_b" LOGICAL 0/00000000 (proto_version '4', streaming 'parallel', origin 'none', publication_names '"tap_pub_b"') 2026-05-06 14:58:50.184 UTC client backend[56522] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:50.185 UTC client backend[56522] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:50.185 UTC client backend[56522] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:50.186 UTC client backend[56522] 035_conflicts.pl LOG: connection ready: setup total=2.997 ms, fork=1.523 ms, authentication=0.124 ms 2026-05-06 14:58:50.186 UTC client backend[56522] 035_conflicts.pl LOG: statement: SELECT * FROM tab; 2026-05-06 14:58:50.189 UTC client backend[56522] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.005 user=admin database=postgres host=[local] 2026-05-06 14:58:50.215 UTC walsender[56498] tap_sub_a_b LOG: released logical replication slot "tap_sub_a_b" 2026-05-06 14:58:50.215 UTC walsender[56498] tap_sub_a_b LOG: disconnection: session time: 0:00:00.161 user=admin database=postgres host=[local] 2026-05-06 14:58:50.263 UTC logical replication apply worker[56534] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:50.277 UTC logical replication apply worker[56534] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:50.277 UTC logical replication apply worker[56534] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:50.277 UTC logical replication apply worker[56534] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:50.282 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56534) exited with exit code 1 2026-05-06 14:58:50.312 UTC client backend[56543] [unknown] LOG: connection received: host=[local] 2026-05-06 14:58:50.313 UTC client backend[56543] [unknown] LOG: connection authenticated: user="admin" method=trust (/Users/admin/pgsql/build/testrun/subscription/035_conflicts/data/t_035_conflicts_subscriber_data/pgdata/pg_hba.conf:117) 2026-05-06 14:58:50.313 UTC client backend[56543] [unknown] LOG: connection authorized: user=admin database=postgres application_name=035_conflicts.pl 2026-05-06 14:58:50.314 UTC client backend[56543] 035_conflicts.pl LOG: connection ready: setup total=4.346 ms, fork=2.285 ms, authentication=0.130 ms 2026-05-06 14:58:50.315 UTC client backend[56543] 035_conflicts.pl LOG: statement: UPDATE tab SET b = 3 WHERE a = 1; 2026-05-06 14:58:50.318 UTC client backend[56543] 035_conflicts.pl LOG: disconnection: session time: 0:00:00.005 user=admin database=postgres host=[local] TRAP: failed Assert("conflictlogrel != NULL"), File: "../src/backend/replication/logical/conflict.c", Line: 195, PID: 56328 0 postgres 0x00000001050358d8 ExceptionalCondition + 108 1 postgres 0x0000000104e74ca8 ReportApplyConflict + 4640 2 postgres 0x0000000104e960b0 apply_handle_delete_internal + 260 3 postgres 0x000000010518c7e4 apply_dispatch.cold.18 + 368 4 postgres 0x0000000104e9298c apply_dispatch + 6660 5 postgres 0x0000000104e93a24 start_apply + 712 6 postgres 0x0000000104e948d8 run_apply_worker + 788 7 postgres 0x0000000104e945bc ApplyWorkerMain + 36 8 postgres 0x0000000104e448dc BackgroundWorkerMain + 472 9 postgres 0x0000000104e48ef8 postmaster_child_launch + 376 10 postgres 0x0000000104e4bd60 maybe_start_bgworkers + 488 11 postgres 0x0000000104e4d974 ServerLoop + 6976 12 postgres 0x0000000104e4b3b8 InitProcessGlobals + 0 13 postgres 0x0000000104d8d5a0 main + 1036 14 dyld 0x0000000180f2eb98 start + 6076 2026-05-06 14:58:50.824 UTC logical replication apply worker[56577] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:51.266 UTC logical replication apply worker[56577] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:51.266 UTC logical replication apply worker[56577] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:51.266 UTC logical replication apply worker[56577] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:51.281 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56577) exited with exit code 1 2026-05-06 14:58:51.289 UTC logical replication apply worker[56581] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:51.396 UTC logical replication apply worker[56581] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:51.396 UTC logical replication apply worker[56581] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:51.396 UTC logical replication apply worker[56581] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:51.398 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56581) exited with exit code 1 2026-05-06 14:58:51.784 UTC logical replication apply worker[56622] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:51.805 UTC logical replication apply worker[56622] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:51.805 UTC logical replication apply worker[56622] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:51.805 UTC logical replication apply worker[56622] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:51.807 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56622) exited with exit code 1 2026-05-06 14:58:52.284 UTC logical replication apply worker[56679] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:52.305 UTC logical replication apply worker[56679] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:52.305 UTC logical replication apply worker[56679] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:52.305 UTC logical replication apply worker[56679] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:52.306 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56679) exited with exit code 1 2026-05-06 14:58:52.794 UTC logical replication apply worker[56722] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:52.860 UTC logical replication apply worker[56722] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:52.860 UTC logical replication apply worker[56722] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:52.860 UTC logical replication apply worker[56722] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:52.863 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56722) exited with exit code 1 2026-05-06 14:58:53.294 UTC logical replication apply worker[56767] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:53.305 UTC logical replication apply worker[56767] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:53.305 UTC logical replication apply worker[56767] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:53.305 UTC logical replication apply worker[56767] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:53.306 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56767) exited with exit code 1 2026-05-06 14:58:53.795 UTC logical replication apply worker[56833] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:53.846 UTC logical replication apply worker[56833] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:53.846 UTC logical replication apply worker[56833] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:53.846 UTC logical replication apply worker[56833] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:53.849 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56833) exited with exit code 1 2026-05-06 14:58:54.292 UTC logical replication apply worker[56878] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:54.300 UTC logical replication apply worker[56878] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:54.300 UTC logical replication apply worker[56878] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:54.300 UTC logical replication apply worker[56878] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:54.301 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56878) exited with exit code 1 2026-05-06 14:58:54.802 UTC logical replication apply worker[56945] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:54.829 UTC logical replication apply worker[56945] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:54.829 UTC logical replication apply worker[56945] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:54.829 UTC logical replication apply worker[56945] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:54.831 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56945) exited with exit code 1 2026-05-06 14:58:55.304 UTC logical replication apply worker[56993] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:55.319 UTC logical replication apply worker[56993] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:55.319 UTC logical replication apply worker[56993] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:55.319 UTC logical replication apply worker[56993] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:55.321 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56993) exited with exit code 1 2026-05-06 14:58:55.826 UTC logical replication apply worker[57044] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:55.851 UTC logical replication apply worker[57044] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:55.851 UTC logical replication apply worker[57044] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:55.851 UTC logical replication apply worker[57044] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:55.854 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57044) exited with exit code 1 2026-05-06 14:58:56.304 UTC logical replication apply worker[57094] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:56.321 UTC logical replication apply worker[57094] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:56.321 UTC logical replication apply worker[57094] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:56.321 UTC logical replication apply worker[57094] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:56.323 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57094) exited with exit code 1 2026-05-06 14:58:56.805 UTC logical replication apply worker[57156] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:56.825 UTC logical replication apply worker[57156] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:56.825 UTC logical replication apply worker[57156] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:56.825 UTC logical replication apply worker[57156] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:56.827 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57156) exited with exit code 1 2026-05-06 14:58:57.320 UTC logical replication apply worker[57204] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:57.393 UTC logical replication apply worker[57204] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:57.393 UTC logical replication apply worker[57204] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:57.393 UTC logical replication apply worker[57204] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:57.398 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57204) exited with exit code 1 2026-05-06 14:58:57.808 UTC logical replication apply worker[57265] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:57.820 UTC logical replication apply worker[57265] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:57.820 UTC logical replication apply worker[57265] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:57.820 UTC logical replication apply worker[57265] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:57.822 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57265) exited with exit code 1 2026-05-06 14:58:58.311 UTC logical replication apply worker[57325] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:58.336 UTC logical replication apply worker[57325] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:58.336 UTC logical replication apply worker[57325] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:58.336 UTC logical replication apply worker[57325] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:58.338 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57325) exited with exit code 1 2026-05-06 14:58:58.818 UTC logical replication apply worker[57385] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:58.851 UTC logical replication apply worker[57385] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:58.851 UTC logical replication apply worker[57385] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:58.851 UTC logical replication apply worker[57385] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:58.857 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57385) exited with exit code 1 2026-05-06 14:58:59.312 UTC logical replication apply worker[57450] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:59.327 UTC logical replication apply worker[57450] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:59.327 UTC logical replication apply worker[57450] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:59.327 UTC logical replication apply worker[57450] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:59.338 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57450) exited with exit code 1 2026-05-06 14:58:59.815 UTC logical replication apply worker[57506] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:58:59.834 UTC logical replication apply worker[57506] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:58:59.834 UTC logical replication apply worker[57506] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:58:59.834 UTC logical replication apply worker[57506] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:58:59.837 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57506) exited with exit code 1 2026-05-06 14:59:00.325 UTC logical replication apply worker[57547] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:00.428 UTC logical replication apply worker[57547] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:00.428 UTC logical replication apply worker[57547] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:00.428 UTC logical replication apply worker[57547] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:00.439 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57547) exited with exit code 1 2026-05-06 14:59:00.823 UTC logical replication apply worker[57591] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:00.859 UTC logical replication apply worker[57591] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:00.859 UTC logical replication apply worker[57591] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:00.859 UTC logical replication apply worker[57591] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:00.868 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57591) exited with exit code 1 2026-05-06 14:59:01.328 UTC logical replication apply worker[57639] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:01.380 UTC logical replication apply worker[57639] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:01.380 UTC logical replication apply worker[57639] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:01.380 UTC logical replication apply worker[57639] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:01.384 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57639) exited with exit code 1 2026-05-06 14:59:01.843 UTC logical replication apply worker[57684] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:01.885 UTC logical replication apply worker[57684] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:01.885 UTC logical replication apply worker[57684] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:01.885 UTC logical replication apply worker[57684] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:01.888 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57684) exited with exit code 1 2026-05-06 14:59:02.336 UTC logical replication apply worker[57732] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:02.447 UTC logical replication apply worker[57732] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:02.447 UTC logical replication apply worker[57732] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:02.447 UTC logical replication apply worker[57732] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:02.464 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57732) exited with exit code 1 2026-05-06 14:59:02.844 UTC logical replication apply worker[57779] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:02.876 UTC logical replication apply worker[57779] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:02.876 UTC logical replication apply worker[57779] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:02.876 UTC logical replication apply worker[57779] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:02.881 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57779) exited with exit code 1 2026-05-06 14:59:03.338 UTC logical replication apply worker[57833] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:03.352 UTC logical replication apply worker[57833] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:03.352 UTC logical replication apply worker[57833] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:03.352 UTC logical replication apply worker[57833] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:03.357 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57833) exited with exit code 1 2026-05-06 14:59:03.847 UTC logical replication apply worker[57889] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:03.871 UTC logical replication apply worker[57889] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:03.871 UTC logical replication apply worker[57889] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:03.871 UTC logical replication apply worker[57889] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:03.874 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57889) exited with exit code 1 2026-05-06 14:59:04.339 UTC logical replication apply worker[57939] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:04.353 UTC logical replication apply worker[57939] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:04.353 UTC logical replication apply worker[57939] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:04.353 UTC logical replication apply worker[57939] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:04.357 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57939) exited with exit code 1 2026-05-06 14:59:04.852 UTC logical replication apply worker[57983] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:04.876 UTC logical replication apply worker[57983] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:04.876 UTC logical replication apply worker[57983] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:04.876 UTC logical replication apply worker[57983] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:04.889 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 57983) exited with exit code 1 2026-05-06 14:59:05.352 UTC logical replication apply worker[58025] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:05.377 UTC logical replication apply worker[58025] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:05.377 UTC logical replication apply worker[58025] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:05.377 UTC logical replication apply worker[58025] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:05.379 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58025) exited with exit code 1 2026-05-06 14:59:05.865 UTC logical replication apply worker[58054] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:05.951 UTC logical replication apply worker[58054] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:05.951 UTC logical replication apply worker[58054] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:05.951 UTC logical replication apply worker[58054] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:05.955 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58054) exited with exit code 1 2026-05-06 14:59:06.373 UTC logical replication apply worker[58081] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:06.411 UTC logical replication apply worker[58081] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:06.411 UTC logical replication apply worker[58081] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:06.411 UTC logical replication apply worker[58081] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:06.419 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58081) exited with exit code 1 2026-05-06 14:59:06.932 UTC logical replication apply worker[58101] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:07.062 UTC logical replication apply worker[58101] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:07.062 UTC logical replication apply worker[58101] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:07.062 UTC logical replication apply worker[58101] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:07.068 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58101) exited with exit code 1 2026-05-06 14:59:07.408 UTC logical replication apply worker[58123] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:07.485 UTC logical replication apply worker[58123] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:07.485 UTC logical replication apply worker[58123] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:07.485 UTC logical replication apply worker[58123] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:07.489 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58123) exited with exit code 1 2026-05-06 14:59:08.150 UTC logical replication apply worker[58163] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:09.080 UTC logical replication apply worker[58163] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:09.080 UTC logical replication apply worker[58163] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:09.080 UTC logical replication apply worker[58163] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:09.381 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58163) exited with exit code 1 2026-05-06 14:59:09.686 UTC logical replication apply worker[58179] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:10.151 UTC logical replication apply worker[58179] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:10.151 UTC logical replication apply worker[58179] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:10.151 UTC logical replication apply worker[58179] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:10.174 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58179) exited with exit code 1 2026-05-06 14:59:10.236 UTC logical replication apply worker[58192] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:10.718 UTC logical replication apply worker[58192] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:10.718 UTC logical replication apply worker[58192] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:10.718 UTC logical replication apply worker[58192] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:10.752 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58192) exited with exit code 1 2026-05-06 14:59:10.793 UTC logical replication apply worker[58205] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:10.829 UTC logical replication apply worker[58205] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:10.829 UTC logical replication apply worker[58205] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:10.829 UTC logical replication apply worker[58205] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:10.831 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58205) exited with exit code 1 2026-05-06 14:59:11.269 UTC logical replication apply worker[58215] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:11.302 UTC logical replication apply worker[58215] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:11.302 UTC logical replication apply worker[58215] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:11.302 UTC logical replication apply worker[58215] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:11.315 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58215) exited with exit code 1 2026-05-06 14:59:11.825 UTC logical replication apply worker[58222] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:11.980 UTC logical replication apply worker[58222] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:11.980 UTC logical replication apply worker[58222] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:11.980 UTC logical replication apply worker[58222] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:12.007 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58222) exited with exit code 1 2026-05-06 14:59:12.473 UTC logical replication apply worker[58227] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:12.542 UTC logical replication apply worker[58227] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:12.542 UTC logical replication apply worker[58227] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:12.542 UTC logical replication apply worker[58227] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:12.544 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58227) exited with exit code 1 2026-05-06 14:59:12.951 UTC logical replication apply worker[58234] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:13.006 UTC logical replication apply worker[58234] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:13.006 UTC logical replication apply worker[58234] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:13.006 UTC logical replication apply worker[58234] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:13.013 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58234) exited with exit code 1 2026-05-06 14:59:13.497 UTC logical replication apply worker[58261] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:13.567 UTC logical replication apply worker[58261] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:13.567 UTC logical replication apply worker[58261] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:13.567 UTC logical replication apply worker[58261] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:13.577 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58261) exited with exit code 1 2026-05-06 14:59:13.963 UTC logical replication apply worker[58289] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:13.999 UTC logical replication apply worker[58289] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:13.999 UTC logical replication apply worker[58289] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:13.999 UTC logical replication apply worker[58289] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:14.001 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58289) exited with exit code 1 2026-05-06 14:59:14.466 UTC logical replication apply worker[58312] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:14.541 UTC logical replication apply worker[58312] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:14.541 UTC logical replication apply worker[58312] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:14.541 UTC logical replication apply worker[58312] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:14.546 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58312) exited with exit code 1 2026-05-06 14:59:14.987 UTC logical replication apply worker[58346] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:15.147 UTC logical replication apply worker[58346] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:15.147 UTC logical replication apply worker[58346] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:15.147 UTC logical replication apply worker[58346] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:15.156 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58346) exited with exit code 1 2026-05-06 14:59:15.496 UTC logical replication apply worker[58374] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:15.526 UTC logical replication apply worker[58374] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:15.526 UTC logical replication apply worker[58374] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:15.526 UTC logical replication apply worker[58374] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:15.540 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58374) exited with exit code 1 2026-05-06 14:59:16.147 UTC logical replication apply worker[58393] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:16.264 UTC logical replication apply worker[58393] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:16.264 UTC logical replication apply worker[58393] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:16.264 UTC logical replication apply worker[58393] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:16.275 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58393) exited with exit code 1 2026-05-06 14:59:16.489 UTC logical replication apply worker[58418] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:16.536 UTC logical replication apply worker[58418] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:16.536 UTC logical replication apply worker[58418] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:16.536 UTC logical replication apply worker[58418] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:16.540 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58418) exited with exit code 1 2026-05-06 14:59:16.988 UTC logical replication apply worker[58446] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:16.999 UTC logical replication apply worker[58446] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:16.999 UTC logical replication apply worker[58446] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:16.999 UTC logical replication apply worker[58446] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:17.000 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58446) exited with exit code 1 2026-05-06 14:59:17.492 UTC logical replication apply worker[58484] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:17.522 UTC logical replication apply worker[58484] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:17.522 UTC logical replication apply worker[58484] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:17.522 UTC logical replication apply worker[58484] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:17.523 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58484) exited with exit code 1 2026-05-06 14:59:17.996 UTC logical replication apply worker[58540] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:18.035 UTC logical replication apply worker[58540] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:18.035 UTC logical replication apply worker[58540] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:18.035 UTC logical replication apply worker[58540] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:18.041 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58540) exited with exit code 1 2026-05-06 14:59:18.494 UTC logical replication apply worker[58585] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:18.531 UTC logical replication apply worker[58585] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:18.531 UTC logical replication apply worker[58585] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:18.531 UTC logical replication apply worker[58585] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:18.533 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58585) exited with exit code 1 2026-05-06 14:59:18.802 UTC autovacuum worker[58600] LOG: automatic analyze of table "postgres.pg_conflict.pg_conflict_log_16410" avg read rate: 8.013 MB/s, avg write rate: 1.402 MB/s buffer usage: 634 hits, 40 reads, 7 dirtied WAL usage: 36 records, 5 full page images, 30742 bytes, 27208 full page image bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2026-05-06 14:59:18.809 UTC autovacuum worker[58600] LOG: automatic vacuum of table "postgres.public.conf_tab_2_p1": index scans: 1 pages: 0 removed, 1 remain, 1 scanned (100.00% of total), 0 eagerly scanned tuples: 58 removed, 1 remain, 0 are dead but not yet removable removable cutoff: 742, which was 109 XIDs old when operation ended new relfrozenxid: 721, which is 26 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 1 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (100.00% of total) had 58 dead item identifiers removed index "conf_tab_2_p1_pkey": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "conf_tab_2_p1_a_b_key": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 1.837 MB/s, avg write rate: 9.183 MB/s buffer usage: 66 hits, 1 reads, 5 dirtied WAL usage: 10 records, 4 full page images, 34760 bytes, 32768 full page image bytes, 0 buffers full memory usage: dead item storage 0.03 MB accumulated across 1 reset (limit 64.00 MB each) system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2026-05-06 14:59:19.060 UTC logical replication apply worker[58613] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:19.127 UTC logical replication apply worker[58613] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:19.127 UTC logical replication apply worker[58613] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:19.127 UTC logical replication apply worker[58613] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:19.131 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58613) exited with exit code 1 2026-05-06 14:59:19.501 UTC logical replication apply worker[58641] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:19.511 UTC logical replication apply worker[58641] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:19.511 UTC logical replication apply worker[58641] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:19.511 UTC logical replication apply worker[58641] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:19.512 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58641) exited with exit code 1 2026-05-06 14:59:20.015 UTC logical replication apply worker[58676] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:20.048 UTC logical replication apply worker[58676] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:20.048 UTC logical replication apply worker[58676] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:20.048 UTC logical replication apply worker[58676] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:20.051 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58676) exited with exit code 1 2026-05-06 14:59:20.513 UTC logical replication apply worker[58719] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:20.581 UTC logical replication apply worker[58719] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:20.581 UTC logical replication apply worker[58719] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:20.581 UTC logical replication apply worker[58719] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:20.602 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58719) exited with exit code 1 2026-05-06 14:59:21.009 UTC logical replication apply worker[58762] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:21.026 UTC logical replication apply worker[58762] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:21.026 UTC logical replication apply worker[58762] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:21.026 UTC logical replication apply worker[58762] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:21.028 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58762) exited with exit code 1 2026-05-06 14:59:21.509 UTC logical replication apply worker[58795] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:21.533 UTC logical replication apply worker[58795] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:21.533 UTC logical replication apply worker[58795] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:21.533 UTC logical replication apply worker[58795] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:21.534 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58795) exited with exit code 1 2026-05-06 14:59:22.022 UTC logical replication apply worker[58840] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:22.065 UTC logical replication apply worker[58840] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:22.065 UTC logical replication apply worker[58840] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:22.065 UTC logical replication apply worker[58840] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:22.076 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58840) exited with exit code 1 2026-05-06 14:59:22.518 UTC logical replication apply worker[58880] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:22.553 UTC logical replication apply worker[58880] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:22.553 UTC logical replication apply worker[58880] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:22.553 UTC logical replication apply worker[58880] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:22.559 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58880) exited with exit code 1 2026-05-06 14:59:23.017 UTC logical replication apply worker[58916] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:23.043 UTC logical replication apply worker[58916] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:23.043 UTC logical replication apply worker[58916] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:23.043 UTC logical replication apply worker[58916] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:23.049 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58916) exited with exit code 1 2026-05-06 14:59:23.517 UTC logical replication apply worker[58962] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:23.581 UTC logical replication apply worker[58962] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:23.581 UTC logical replication apply worker[58962] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:23.581 UTC logical replication apply worker[58962] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:23.584 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 58962) exited with exit code 1 2026-05-06 14:59:24.024 UTC logical replication apply worker[59003] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:24.050 UTC logical replication apply worker[59003] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:24.050 UTC logical replication apply worker[59003] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:24.050 UTC logical replication apply worker[59003] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:24.051 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59003) exited with exit code 1 2026-05-06 14:59:24.524 UTC logical replication apply worker[59056] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:24.565 UTC logical replication apply worker[59056] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:24.565 UTC logical replication apply worker[59056] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:24.565 UTC logical replication apply worker[59056] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:24.567 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59056) exited with exit code 1 2026-05-06 14:59:25.041 UTC logical replication apply worker[59113] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:25.076 UTC logical replication apply worker[59113] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:25.076 UTC logical replication apply worker[59113] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:25.076 UTC logical replication apply worker[59113] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:25.078 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59113) exited with exit code 1 2026-05-06 14:59:25.536 UTC logical replication apply worker[59150] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:25.578 UTC logical replication apply worker[59150] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:25.578 UTC logical replication apply worker[59150] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:25.578 UTC logical replication apply worker[59150] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:25.581 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59150) exited with exit code 1 2026-05-06 14:59:26.032 UTC logical replication apply worker[59204] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:26.044 UTC logical replication apply worker[59204] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:26.044 UTC logical replication apply worker[59204] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:26.044 UTC logical replication apply worker[59204] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:26.046 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59204) exited with exit code 1 2026-05-06 14:59:26.536 UTC logical replication apply worker[59254] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:26.610 UTC logical replication apply worker[59254] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:26.610 UTC logical replication apply worker[59254] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:26.610 UTC logical replication apply worker[59254] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:26.613 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59254) exited with exit code 1 2026-05-06 14:59:27.037 UTC logical replication apply worker[59295] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:27.058 UTC logical replication apply worker[59295] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:27.058 UTC logical replication apply worker[59295] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:27.058 UTC logical replication apply worker[59295] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:27.059 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59295) exited with exit code 1 2026-05-06 14:59:27.538 UTC logical replication apply worker[59347] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:27.588 UTC logical replication apply worker[59347] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:27.588 UTC logical replication apply worker[59347] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:27.588 UTC logical replication apply worker[59347] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:27.594 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59347) exited with exit code 1 2026-05-06 14:59:28.036 UTC logical replication apply worker[59404] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:28.047 UTC logical replication apply worker[59404] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:28.047 UTC logical replication apply worker[59404] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:28.047 UTC logical replication apply worker[59404] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:28.048 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59404) exited with exit code 1 2026-05-06 14:59:28.540 UTC logical replication apply worker[59450] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:28.577 UTC logical replication apply worker[59450] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:28.577 UTC logical replication apply worker[59450] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:28.577 UTC logical replication apply worker[59450] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:28.581 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59450) exited with exit code 1 2026-05-06 14:59:29.040 UTC logical replication apply worker[59497] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:29.069 UTC logical replication apply worker[59497] ERROR: conflict detected on relation "public.conf_tab_2_p1": conflict=multiple_unique_conflicts 2026-05-06 14:59:29.069 UTC logical replication apply worker[59497] DETAIL: Could not apply remote change: remote row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_pkey", modified in transaction 721: key (a)=(55), local row (55, 2, 3). Key already exists in unique index "conf_tab_2_p1_a_b_key", modified in transaction 721: key (a, b)=(55, 2), local row (55, 2, 3). 2026-05-06 14:59:29.069 UTC logical replication apply worker[59497] CONTEXT: processing remote data for replication origin "pg_16410" during message type "INSERT" for replication target relation "public.conf_tab_2" in transaction 700, finished at 0/017DB1D0 2026-05-06 14:59:29.078 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 59497) exited with exit code 1 2026-05-06 14:59:29.542 UTC logical replication apply worker[59526] LOG: logical replication apply worker for subscription "sub_tab" has started 2026-05-06 14:59:29.543 UTC postmaster[56273] LOG: background worker "logical replication apply worker" (PID 56328) was terminated by signal 6: Abort trap: 6 2026-05-06 14:59:29.549 UTC postmaster[56273] LOG: terminating any other active server processes 2026-05-06 14:59:29.555 UTC postmaster[56273] LOG: shutting down because "restart_after_crash" is off 2026-05-06 14:59:29.559 UTC postmaster[56273] LOG: database system is shut down