RE: Conflict detection for update_deleted in logical replication

[Zhijie Hou (Fujitsu)]

On Wednesday, July 23, 2025 12:08 PM Amit Kapila <amit.kapil...@gmail.com> 
wrote:
> 
> On Wed, Jul 23, 2025 at 3:51 AM Masahiko Sawada
> <sawada.m...@gmail.com> wrote:
> >
> > I've reviewed the 0001 patch and it looks good to me.
> >
> 
> Thanks, I have pushed the 0001 patch.

Thanks for pushing. I have rebased the remaining patches.

I have reordered the patches to prioritize the detection of update_deleted as
the initial patch. This can give us more time to consider the new GUC, since the
performance-related aspects have been documented.

One pervious patch used to prove the possibility of allowing changing the
retain_dead_tuples for enabled subscription, has not yet been rebased. I will
rebase that once all the main patches are stable.

Best Regards,
Hou zj

v52-0003-Re-create-the-replication-slot-if-the-conflict-r.patch
Description: v52-0003-Re-create-the-replication-slot-if-the-conflict-r.patch

v52-0001-Support-the-conflict-detection-for-update_delete.patch
Description: v52-0001-Support-the-conflict-detection-for-update_delete.patch

v52-0002-Introduce-a-new-GUC-max_conflict_retention_durat.patch
Description: v52-0002-Introduce-a-new-GUC-max_conflict_retention_durat.patch