Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber
От | Amit Kapila |
---|---|
Тема | Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber |
Дата | |
Msg-id | CAA4eK1KjgViaqQGR6897+20Z_zOARr4CrZr06jmc3Euq22453Q@mail.gmail.com обсуждение исходный текст |
Ответ на | [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>) |
Ответы |
Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber
|
Список | pgsql-hackers |
On Tue, Aug 20, 2024 at 2:01 PM shveta malik <shveta.malik@gmail.com> wrote: > > On Tue, Aug 20, 2024 at 11:36 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Wed, Aug 14, 2024 at 10:26 AM shveta malik <shveta.malik@gmail.com> wrote: > > > > > > > > > > > Thanks for the detailed analysis. I agree with your analysis that we > > > > need to reset the origin information for the shutdown path to avoid it > > > > being advanced incorrectly. However, the patch doesn't have sufficient > > > > comments to explain why we need to reset it for both the ERROR and > > > > Shutdown paths. Can we improve the comments in the patch? > > > > > > > > Also, for the ERROR path, can we reset the origin information in > > > > apply_error_callback()? > > > > > > Please find v4 attached. Addressed comments in that. > > > > > > > The patch looks mostly good to me. I have slightly changed a few of > > the comments in the attached. What do you think of the attached? > > > > Looks good to me. Please find backported patches attached. > Pushed. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: