Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_decode_message vs skip_empty_xacts and xact_wrote_changes
Date: 2023-07-11 15:00:41
Message-ID: CAExHW5sA0BNpPyC6AwiobojTePw90Eu0ZTCbJcQJFZKO1cfi-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 11, 2023 at 5:59 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

> >
>
> I have pushed this work. But feel free to propose further
> improvements, if you have any better ideas.
>

Thanks. We have fixed the problem. So things are better than they
were. I have been busy with something else so couldn't reply.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2023-07-11 15:04:44 Re: Forgive trailing semicolons inside of config files
Previous Message Tristan Partin 2023-07-11 14:58:11 Re: Make pgbench exit on SIGINT more reliably