Request a Demo
Home   >   mailing lists

Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load - Mailing list pgsql-bugs

From vignesh C
Subject Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
Date
Msg-id CALDaNm1zpOm7ezD17nZGxp_vs6z4uMzRc54D=Ofw-GaAc7bJ0g@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load  (Shlok Kyal <shlok.kyal.oss@gmail.com>)
List pgsql-bugs
Tree view 
On Sun, 11 May 2025 at 00:49, Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> Thanks for providing the patch. I have verified the original case with
> the patch on both HEAD and PG_17.
> With the changes in [1], I noticed that even if the consistent lsn is
> set to 'COMMIT' record, we do not get data mismatches or the primary
> key conflict.
> I have also attached the logs for test runs with your changes.
>
> I have also attached the patches which apply on HEAD and PG_17.

The changes look good to me, I don't have any more comments.

Regards,
Vignesh

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform
Next
From: PG Bug reporting form
Date:
Subject: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost