Re: Backward movement of confirmed_flush resulting in data duplication. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Backward movement of confirmed_flush resulting in data duplication.
Date
Msg-id CAA4eK1J3eci33mS3ZNh208e0pG=+7YeecBJda4o=3u_b1GFoow@mail.gmail.com
Whole thread Raw
List pgsql-hackers
On Fri, May 16, 2025 at 5:39 PM Nisha Moond <nisha.moond412@gmail.com> wrote:
>
> Hi,
>
> On Tue, May 13, 2025 at 3:48 PM shveta malik <shveta.malik@gmail.com> wrote:
> >
> >
> > With the given script, the problem reproduces on Head and PG17. We are
> > trying to reproduce the issue on PG16 and below where injection points
> > are not there.
> >
>
> The issue can also be reproduced on PostgreSQL versions 13 through 16.
>

Thanks. I have pushed the fix.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Next
From: Aleksander Alekseev
Date:
Subject: Re: Should we optimize the `ORDER BY random() LIMIT x` case?