Re: Conflict detection and logging in logical replication - Mailing list pgsql-hackers

From Michail Nikolaev
Subject Re: Conflict detection and logging in logical replication
Date
Msg-id CANtu0ojDYgHpDiJUbGEnK7TsxVauVNsF0O1XhyceojRf=8Ni_A@mail.gmail.com
Whole thread Raw
In response to RE: Conflict detection and logging in logical replication  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
Responses RE: Conflict detection and logging in logical replication
List pgsql-hackers
Hello!

> I think this is an independent issue which can be discussed separately in the
> original thread[1], and I have replied to that thread.

Thanks! But it seems like this part is still relevant to the current thread:

> It also seems possible that a conflict could be resolved by a concurrent update
> before the call to CheckAndReportConflict, which means there's no guarantee
> that the conflict will be reported correctly. Should we be concerned about
> this?

Best regards,
Mikhail.

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Thread-safe nl_langinfo() and localeconv()
Next
From: Thomas Munro
Date:
Subject: Re: Thread-safe nl_langinfo() and localeconv()