| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Document slot's restart_lsn can go backward |
| Date: | 2025-07-19 12:47:28 |
| Message-ID: | CAPpHfdtN-FdAwUxo4L63LZCoXDyhwAO-DaW-WzK0pknA8VeOqQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 18, 2025 at 2:40 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?
If nobody has additions/objections, I'll push this change.
------
Regards,
Alexander Korotkov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-07-19 13:07:16 | Re: index prefetching |
| Previous Message | Amit Kapila | 2025-07-19 11:39:49 | Re: Improve pg_sync_replication_slots() to wait for primary to advance |