On Thu, Aug 1, 2024 at 2:26 PM Hayato Kuroda (Fujitsu) <kuroda.hay...@fujitsu.com> wrote: > > 04. general > > According to the documentation [1], there is another constraint "exclude", > which > can cause another type of conflict. But this pattern cannot be logged in > detail. >
As per docs, "exclusion constraints can specify constraints that are more general than simple equality", so I don't think it satisfies the kind of conflicts we are trying to LOG and then in the future patch allows automatic resolution for the same. For example, when we have last_update_wins strategy, we will replace the rows with remote rows when the key column values match which shouldn't be true in general for exclusion constraints. Similarly, we don't want to consider other constraint violations like CHECK to consider as conflicts. We can always extend the basic functionality for more conflicts if required but let's go with reporting straight-forward stuff first. -- With Regards, Amit Kapila.
