| From: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Subject: | Re: Conflict detection for multiple_unique_conflicts in logical replication |
| Date: | 2025-03-13 11:00:00 |
| Message-ID: | CABdArM5yDuebLM=ipqXk004bPfWqowX5B4wSm6WMdK1hGAx7Wg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
For v3, CFbot failed for the patch test case due to unstable test
steps. Truncating the subscriber table resolved the apply worker error
but sometimes caused out-of-order inserts, leading to unexpected
failures instead of a conflict error. Fixed this and updated the LOG
regex check to avoid false positives.
Note: I have broken down the full error detail message check into
multiple checks to avoid very long lines in the file. I'll see if
there's a better way to compare the full error detail in a single
check.
Attached is the v4 patch (test case changes only).
--
Thanks,
Nisha Moond
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Implement-the-conflict-detection-for-multiple_uni.patch | application/octet-stream | 23.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-03-13 11:03:29 | Re: Changing the state of data checksums in a running cluster |
| Previous Message | Timur Magomedov | 2025-03-13 10:54:45 | Re: Minor rework of ALTER TABLE SET RelOptions code |