Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
От | Alexander Korotkov |
---|---|
Тема | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |
Дата | |
Msg-id | CAPpHfdtgwhFFpb8v8x2Humdj3F_DjaeBWY_h20g-Owh5tMArCA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
|
Список | pgsql-hackers |
On Tue, Apr 29, 2025 at 4:03 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Mon, Apr 28, 2025 at 8:17 AM Alexander Korotkov <aekorotkov@gmail.com> wrote: > > > > > I have a question - is there any interest to backport the solution into > > > existing major releases? > > > > As long as this is the bug, it should be backpatched to all supported > > affected releases. > > Yes, but I think we cannot back-patch the proposed fix to back > branches as it changes the ReplicationSlot struct defined in slot.h, > which breaks ABI compatibility. Yes, and I think Vitaly already proposed to address this issue. This aspect also needs to be carefully reviewed for sure. On Thu, Apr 24, 2025 at 5:32 PM Vitaly Davydov <v.davydov@postgrespro.ru> wrote: > I can prepare a patch where restart_lsn_flushed stored > outside of ReplicationSlot structure and doesn't affect the existing API. ------ Regards, Alexander Korotkov Supabase
В списке pgsql-hackers по дате отправления: