Re: Conflict detection and logging in logical replication

From: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, shveta malik <shveta(dot)malik(at)gmail(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-13 11:32:33
Message-ID: CANtu0ojDYgHpDiJUbGEnK7TsxVauVNsF0O1XhyceojRf=8Ni_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2024-08-13 11:39:45 Re: Thread-safe nl_langinfo() and localeconv()
Previous Message Thomas Munro 2024-08-13 11:25:04 Re: Thread-safe nl_langinfo() and localeconv()