Re: Document slot's restart_lsn can go backward

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Document slot's restart_lsn can go backward
Date: 2025-07-21 12:09:05
Message-ID: CAPpHfdufO1F7sxbzY7Fg4x-ARtkZt+ajD9GfDRcDCaYmTX9Rjw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 21, 2025 at 11:40 AM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> On Mon, 21 Jul 2025 at 11:04, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > On Fri, Jul 18, 2025 at 5:11 PM Alexander Korotkov <aekorotkov(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2025-07-21 12:21:35 Re: Improve error reporting in 027_stream_regress test
Previous Message Nisha Moond 2025-07-21 11:49:11 Re: Conflict detection for update_deleted in logical replication