Horton

RE: Conflict detection and logging in logical replication

Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>

View thread View on postgr.es
From: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
To: Amit Kapila <amit.kapila16@gmail.com>, shveta malik <shveta.malik@gmail.com>
Cc: "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>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Date: 2024-08-20T11:15:24Z
Lists: pgsql-hackers

Attachments

On Tuesday, August 20, 2024 12:37 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> 
> On Mon, Aug 19, 2024 at 4:16 PM Amit Kapila <amit.kapila16@gmail.com>
> Pushed.

Thanks for pushing.

Here are the remaining patches.

0001 adds additional doc to explain the log format.
0002 collects statistics about conflicts in logical replication.

Best Regards,
Hou zj

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.