Re: [PATCH] Present all committed transaction to the output plugin

On Fri, Feb 19, 2021 at 6:06 PM Markus Wanner
<markus(dot)wanner(at)enterprisedb(dot)com> wrote:
>
> Hi,
>
> attached is a patch that I think is cleaning up the API between Postgres
> and the logical decoding plugin. Up until now, not only transactions
> rolled back, but also some committed transactions were filtered and not
> presented to the output plugin. While it is documented that aborted
> transactions are not decoded, the second exception has not been documented.
>
> The difference is with committed empty transactions that have a snapshot
> versus those that do not. I think that's arbitrary and propose to
> remove this distinction, so that all committed transactions are decoded.
>

What exactly is the use case to send empty transactions with or
without prepared? In the past, there was a complaint [1] that such
transactions increase the network traffic.

[1] - https://www.postgresql.org/message-id/CAMkU%3D1yohp9-dv48FLoSPrMqYEyyS5ZWkaZGD41RJr10xiNo_Q%40mail.gmail.com

--
With Regards,
Amit Kapila.