| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> |
| Cc: | 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-05-14 05:30:39 |
| Message-ID: | CALDaNm1zpOm7ezD17nZGxp_vs6z4uMzRc54D=Ofw-GaAc7bJ0g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, 11 May 2025 at 00:49, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-05-14 08:18:45 | BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost |
| Previous Message | PG Bug reporting form | 2025-05-14 03:27:14 | BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform |