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>, Nisha Moond <nisha.moond412@gmail.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Dilip Kumar <dilipbalaut@gmail.com>, shveta malik <shveta.malik@gmail.com>, Jan Wieck <jan@wi3ck.info>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Amit Kapila <amit.kapila16@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

Date: 2024-07-03T03:00:50Z

Lists: pgsql-hackers

Attachments

v4-0002-Collect-statistics-about-conflicts-in-logical-rep.patch (application/octet-stream) patch v4-0002
v4-0001-Detect-and-log-conflicts-in-logical-replication.patch (application/octet-stream) patch v4-0001

On Wednesday, June 26, 2024 10:58 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com> wrote:
>

Hi,

As suggested by Sawada-san in another thread[1].

I am attaching the V4 patch set which tracks the delete_differ
conflict in logical replication.

delete_differ means that the replicated DELETE is deleting a row
that was modified by a different origin.

[1] https://www.postgresql.org/message-id/CAD21AoDzo8ck57nvRVFWOCsjWBCjQMzqTFLY4cCeFeQZ3V_oQg%40mail.gmail.com

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