Horton

Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Euler Taveira <euler@eulerto.com>
Cc: David Pirotte <dpirotte@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Dave Cramer <davecramer@gmail.com>, Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Date: 2021-04-07T05:20:50Z
Lists: pgsql-hackers 
On Mon, Apr 5, 2021 at 5:45 PM Euler Taveira <euler@eulerto.com> wrote:
>
> On Mon, Apr 5, 2021, at 4:06 AM, Amit Kapila wrote:
>
> I have made few minor changes in the attached. (a) Initialize the
> streaming message callback API, (b) update docs to reflect that XID
> can be sent for streaming of in-progress transactions, I see that the
> same information needs to be updated for a few other protocol message
> but we can do that as a separate patch (c) slightly tweaked the commit
> messages
>
> Good catch. I completely forgot the streaming of in progress transactions. I
> agree that the documentation for transaction should be added as a separate
> patch since the scope is beyond this feature.
>

I have pushed this work and updated the CF entry accordingly.

-- 
With Regards,
Amit Kapila.

Commits

  1. Allow pgoutput to send logical decoding messages.

  2. Refactor function parse_output_parameters.