Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, duffieldzane(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
Date: 2025-07-24 10:49:02
Message-ID: CAA4eK1KzUWDLbAyxob32Vbs5Q6VGrD41yCPnMrrLCc-THjK6pg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 23, 2025 at 6:56 PM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> wrote:
>
> >
> Thanks for reviewing the patch. I have added comments and attached the
> updated patch.
> v6_HEAD applies to HEAD and REL_18_STABLE. v6_REL_17 applies to REL_17_STABLE.
>

Thanks, I have pushed the fix after changing the comments.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Patrick Stählin 2025-07-24 13:46:12 Re: BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18
Previous Message Andrew Watkins 2025-07-24 10:28:05 Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message