Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-19 Thread Amit Kapila
On Fri, May 16, 2025 at 5:39 PM Nisha Moond wrote: > > Hi, > > On Tue, May 13, 2025 at 3:48 PM shveta malik 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. > > >

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-16 Thread Nisha Moond
Hi, On Tue, May 13, 2025 at 3:48 PM shveta malik 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.

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-14 Thread Dilip Kumar
On Wed, May 14, 2025 at 9:16 AM Amit Kapila wrote: > > On Tue, May 13, 2025 at 4:22 PM Dilip Kumar wrote: > > > > On Tue, May 13, 2025 at 3:48 PM shveta malik wrote: > > > > > > Hi All, > > > > > > It is a spin-off thread from earlier discussions at [1] and [2]. > > > > > > While analyzing the s

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-14 Thread Dilip Kumar
On Wed, May 14, 2025 at 12:15 PM Amit Kapila wrote: > > On Wed, May 14, 2025 at 11:59 AM Dilip Kumar wrote: > > > > On Wed, May 14, 2025 at 9:16 AM Amit Kapila wrote: > > > > > > On Tue, May 13, 2025 at 4:22 PM Dilip Kumar wrote: > > > > > > > > On Tue, May 13, 2025 at 3:48 PM shveta malik >

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-13 Thread Amit Kapila
On Wed, May 14, 2025 at 11:59 AM Dilip Kumar wrote: > > On Wed, May 14, 2025 at 9:16 AM Amit Kapila wrote: > > > > On Tue, May 13, 2025 at 4:22 PM Dilip Kumar wrote: > > > > > > On Tue, May 13, 2025 at 3:48 PM shveta malik > > > wrote: > > > > > > > > Hi All, > > > > > > > > It is a spin-off t

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-13 Thread Alexander Kukushkin
Hi Dilip, On Wed, 14 May 2025 at 08:29, Dilip Kumar wrote: > What I meant wasn’t that the subscriber is moving the confirmed LSN > backward, nor was I suggesting we fix it by persisting the LSN on the > subscriber side. My point was: the fact that the subscriber is sending > an LSN older than on

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-13 Thread Amit Kapila
On Tue, May 13, 2025 at 4:22 PM Dilip Kumar wrote: > > On Tue, May 13, 2025 at 3:48 PM shveta malik wrote: > > > > Hi All, > > > > It is a spin-off thread from earlier discussions at [1] and [2]. > > > > While analyzing the slot-sync BF failure as stated in [1], it was > > observed that there are

Re: Backward movement of confirmed_flush resulting in data duplication.

2025-05-13 Thread Dilip Kumar
On Tue, May 13, 2025 at 3:48 PM shveta malik wrote: > > Hi All, > > It is a spin-off thread from earlier discussions at [1] and [2]. > > While analyzing the slot-sync BF failure as stated in [1], it was > observed that there are chances that confirmed_flush_lsn may move > backward depending on the

Backward movement of confirmed_flush resulting in data duplication.

2025-05-13 Thread shveta malik
Hi All, It is a spin-off thread from earlier discussions at [1] and [2]. While analyzing the slot-sync BF failure as stated in [1], it was observed that there are chances that confirmed_flush_lsn may move backward depending on the feedback messages received from the downstream system. It was susp