RE: Conflict detection and logging in logical replication

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

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

To: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, Amit Kapila <amit.kapila16@gmail.com>

Cc: shveta malik <shveta.malik@gmail.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-01T06:09:41Z

Lists: pgsql-hackers

Attachments

v10-0003-Collect-statistics-about-conflicts-in-logical-re.patch (application/octet-stream) patch v10-0003
v10-0001-Detect-and-log-conflicts-in-logical-replication.patch (application/octet-stream) patch v10-0001
v10-0002-Add-a-detect_conflict-option-to-subscriptions.patch (application/octet-stream) patch v10-0002

On Thursday, August 1, 2024 11:40 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
> Here is the V9 patch set which addressed above and Shveta's comments.
> 

The patch conflict with a recent commit a67da49, so here is rebased V10 patch set. 

Thanks to the commit a67da49, I have removed the special check for
cross-partition update in apply_handle_delete_internal() because this function
will not be called in cross-update anymore.

Best Regards,
Hou zj

Commits

Rename the conflict types for the origin differ cases.
- 640178c92e3f 18.0 landed
Doc: explain the log format of logical replication conflicts.
- edcb71258504 18.0 landed
Log the conflicts while applying changes in logical replication.
- 9758174e2e5c 18.0 landed
Avoid duplicate table scans for cross-partition updates during logical replication.
- a67da49e1d98 18.0 cited