Horton

Re: Backward movement of confirmed_flush resulting in data duplication.

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Nisha Moond <nisha.moond412@gmail.com>
Cc: shveta malik <shveta.malik@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
Date: 2025-05-19T09:43:19Z
Lists: 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.

Commits

  1. Don't retreat slot's confirmed_flush LSN.