Re: Conflict detection for update_deleted in logical replication

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Conflict detection for update_deleted in logical replication
Date: 2025-06-27 08:07:20
Message-ID: CAJpy0uDhgVt4wX67UiegLsJ1frX=xmrDcNc9kz+wE7XJ=3_PXw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 27, 2025 at 7:58 AM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Thu, Jun 26, 2025 at 4:28 PM shveta malik wrote:
> >
> > On Thu, Jun 26, 2025 at 8:31 AM Zhijie Hou (Fujitsu)
> > <houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> > >
> > > Thanks for the comments. All of them look good to me and
> > > have been addressed in V42.
> > >
> >
> > Thank You for the patches. Few comments.
> >
> > t/035_conflicts.pl:
> >
> > 1)
> > Both the subscriptions subname_BA and subname_AB have rci enabled
> > during CREATE sub itself. And later in the second test, we are trying
> > to enable rci of subname_AB to test WARNING and NOTICE, but rci is
> > already enabled. Shall we have one CREATE sub with rci enabled while
> > another CREATE sub with default rci. And then we try to enable rci of
> > the second sub later and check pg_conflict_detection slot has been
> > created once we enabled rci. This way, it will cover more scenarios.
>
> Agreed and changed as suggested. I removed the test for WARNING since the
> message is the same as the NOITCE and it seems not worthwhile to disable
> the subscription again to verify one message.
>

Okay. Agreed.

patch001 looks good to me now.

thanks
Shveta

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-06-27 08:11:47 Re: ALTER TABLE ALTER CONSTRAINT misleading error message
Previous Message Zane Duffield 2025-06-27 07:42:41 Check for existing replication slot in pg_createsubscriber