Re: Newly created replication slot may be invalidated by checkpoint
| От | Amit Kapila |
|---|---|
| Тема | Re: Newly created replication slot may be invalidated by checkpoint |
| Дата | |
| Msg-id | CAA4eK1+jz8tM1=o6JGpBpgXwfo-eGZ==wWaQYd4RZ7eFXYwtoQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Newly created replication slot may be invalidated by checkpoint (Masahiko Sawada <sawada.mshk@gmail.com>) |
| Ответы |
RE: Newly created replication slot may be invalidated by checkpoint
|
| Список | pgsql-hackers |
On Mon, Dec 8, 2025 at 12:53 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Fri, Dec 5, 2025 at 4:10 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Thu, Dec 4, 2025 at 12:12 PM Zhijie Hou (Fujitsu) > > <houzj.fnst@fujitsu.com> wrote: > > > > > > Here are the updated patches for HEAD and 18. I did not add tests since, after > > > applying the patch and resolving the issue, the only observable behavior is that > > > the checkpoint will wait for another backend to create a slot due to the lwlock > > > lock, so it seems not worth to test solely lwlock wait event (I could not find similar > > > tests). > > > > > > > Fair enough. The patch looks mostly good to me, attached are minor > > comment improvements atop the HEAD patch. I'll do some more testing > > before push. > > > > Sawada-san/Vitaly, do you have any opinion on patch or the direction > > to fix? The idea is to get this fixed for HEAD and 18, then continue > > discussion for other bank-branches and the remaining patches. > > +1 > Thanks, Pushed. I'll continue thinking on how to fix it in branches prior to 18 and other problems reported in this thread. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: