Re: Document slot's restart_lsn can go backward - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Document slot's restart_lsn can go backward
Date
Msg-id CAPpHfdufO1F7sxbzY7Fg4x-ARtkZt+ajD9GfDRcDCaYmTX9Rjw@mail.gmail.com
Whole thread Raw
In response to Re: Document slot's restart_lsn can go backward  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On Mon, Jul 21, 2025 at 11:40 AM vignesh C <vignesh21@gmail.com> wrote:
>
> On Mon, 21 Jul 2025 at 11:04, Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > On Fri, Jul 18, 2025 at 5:11 PM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> > >
> > > While working on the patch fixing the situation when slot's
> > > restart_lsn ends up pointing to a removed WAL segment [1], we
> > > discovered that sometimes slot's restart_lsn can go backward
> > > [2][3][4].  Hayato Kuroda proposed a patch [5], which improves
> > > comments by describing this behavior.  As proposed by Amit Kapila [6],
> > > I'm starting a new thread about this comments patch.
> > >
> > > Any feedback on this patch?
> > >
> >
> > I have tried to slightly improve the comments. You can include the
> > suggestions, if you and/or kuroda-san thinks that the suggestions make
> > the patch better.
>
> Your changes look good to me.

Pushed!
Thanks to everybody involved.

------
Regards,
Alexander Korotkov
Supabase



pgsql-hackers by date:

Previous
From: Nisha Moond
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Improve error reporting in 027_stream_regress test