| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Cc: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Jan Wieck <jan(at)wi3ck(dot)info>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Subject: | Re: Conflict detection and logging in logical replication |
| Date: | 2024-08-22 08:02:52 |
| Message-ID: | CAHut+PuXmKT4FeGTAOW5rj4p9Tdh3Q_a1=d4zvXWyOCBm-6JJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frédéric Yhuel | 2024-08-22 08:10:53 | pgstattuple: fix free space calculation |
| Previous Message | Yugo NAGATA | 2024-08-22 07:59:47 | Re: Disallow USING clause when altering type of generated column |