RE: Conflict detection for update_deleted in logical replication - Mailing list pgsql-hackers

From Zhijie Hou (Fujitsu)
Subject RE: Conflict detection for update_deleted in logical replication
Date
Msg-id OS9PR01MB169130E31CDDA3A1D16360A12943BA@OS9PR01MB16913.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Conflict detection for update_deleted in logical replication  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
Responses Re: Conflict detection for update_deleted in logical replication
Re: Conflict detection for update_deleted in logical replication
List pgsql-hackers
On Wednesday, August 27, 2025 11:30 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com> wrote:
> 
> Here is V66 patch set which includes the following changes:
> 
> [0001]
> * Enhanced documentation according to Dilip's comments [1].
> * Simplified logic by directly using the leader's oldest_nonremovable_xid to
>   locate deleted tuples, according to Amit's comments [2].
> * Merged Amit's diff [2].
> * Integrated the new NOTICE into the existing CheckSubDeadTupleRetention
>   function according to Amit's feedback [3].
> * Some other adjustments according to feedback from [2] [3].
> 
> [0002]
> * Refactored code according to Shveta's comments [4].
> * Removed an unnecessary variable according to Shveta's suggestions [5].
> * Some other adjustments according to feedback from [4][5][6].

I noticed that Cfbot failed to compile the document due to a typo after renaming
the subscription option. Here are the updated V67 patches to fix that, only the doc
in 0001 is modified.

Best Regards,
Hou zj

Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Mark ItemPointer parameters as const in tuple/table lock functions
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: POC: enable logical decoding when wal_level = 'replica' without a server restart