Re: Document slot's restart_lsn can go backward

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

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.

--
With Regards,
Amit Kapila.

Attachment Content-Type Size
v2-0001-Update-comment-for-last_saved_restart_lsn.patch application/octet-stream 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2025-07-21 05:38:11 Re-archive the WAL on standby with archive_mode=always?
Previous Message Shubham Khanna 2025-07-21 05:30:30 Add support for specifying tables in pg_createsubscriber.