Horton

Re: Conflict detection and logging in logical replication

shveta malik <shveta.malik@gmail.com>

View thread View on postgr.es
From: shveta malik <shveta.malik@gmail.com>
To: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Nisha Moond <nisha.moond412@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Dilip Kumar <dilipbalaut@gmail.com>, Jan Wieck <jan@wi3ck.info>, Peter Smith <smithpb2250@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, shveta malik <shveta.malik@gmail.com>
Date: 2024-08-28T05:53:01Z
Lists: pgsql-hackers 
On Wed, Aug 28, 2024 at 9:44 AM Zhijie Hou (Fujitsu)
<houzj.fnst@fujitsu.com> wrote:
>
> > > +1 on 'update_origin_differs' instead of 'update_origins_differ' as
> > > the former is somewhat similar to other conflict names 'insert_exists'
> > > and 'update_exists'.
> >
> > Since we reached a consensus on this, I am attaching a small patch to rename
> > as suggested.
>
> Sorry, I attached the wrong patch. Here is correct one.
>

LGTM.

thanks
Shveta

Commits

  1. Rename the conflict types for the origin differ cases.

  2. Doc: explain the log format of logical replication conflicts.

  3. Log the conflicts while applying changes in logical replication.

  4. Avoid duplicate table scans for cross-partition updates during logical replication.