Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes
От | Ashutosh Bapat |
---|---|
Тема | Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes |
Дата | |
Msg-id | CAExHW5tcfvvwrKP4TtHFetBd0mc3CPpjsSDbjz3HYQJCcGc4JA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes
|
Список | pgsql-hackers |
On Wed, Jul 5, 2023 at 2:29 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Wed, Jul 5, 2023 at 2:28 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Mon, Jul 3, 2023 at 4:49 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > +1 for the first version patch, I also felt the first version is > > > easily understandable. > > > > > > > Okay, please find the slightly updated version (changed a comment and > > commit message). Unless there are more comments, I'll push this in a > > day or two. > > > > oops, forgot to attach the patch. I still think that we need to do something so that a new call to pg_output_begin() automatically takes care of the conditions under which it should be called. Otherwise, we will introduce a similar problem in some other place in future. -- Best Wishes, Ashutosh Bapat
В списке pgsql-hackers по дате отправления: