Hi Hou-san. I was experimenting with some conflict logging and found that large column values are truncated in the log DETAIL.
E.g. Below I have a table where I inserted a 3000 character text value 'bigbigbig..." Then I caused a replication conflict. test_sub=# delete fr2024-08-22 17:50:17.181 AEST [14901] LOG: logical replication apply worker for subscription "sub1" has started 2024-08-22 17:50:17.193 AEST [14901] ERROR: conflict detected on relation "public.t1": conflict=insert_exists 2024-08-22 17:50:17.193 AEST [14901] DETAIL: Key already exists in unique index "t1_pkey", modified in transaction 780. Key (a)=(k3); existing local tuple (k3, bigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigbigb...); remote tuple (k3, this will clash). ~ Do you think the documentation for the 'column_value' parameter of the conflict logging should say that the displayed value might be truncated? ====== Kind Regards, Peter Smith. Fujitsu Australia
