Re: Conflict detection for multiple_unique_conflicts in logical replication - Mailing list pgsql-hackers

From Nisha Moond
Subject Re: Conflict detection for multiple_unique_conflicts in logical replication
Date
Msg-id CABdArM5yDuebLM=ipqXk004bPfWqowX5B4wSm6WMdK1hGAx7Wg@mail.gmail.com
Whole thread Raw
In response to Re: Conflict detection for multiple_unique_conflicts in logical replication  (Nisha Moond <nisha.moond412@gmail.com>)
Responses Re: Conflict detection for multiple_unique_conflicts in logical replication
List 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

pgsql-hackers by date:

Previous
From: Timur Magomedov
Date:
Subject: Re: Minor rework of ALTER TABLE SET RelOptions code
Next
From: Tomas Vondra
Date:
Subject: Re: Changing the state of data checksums in a running cluster