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-05T07:06:07Z
Lists: pgsql-hackers

Attachments

On Sat, Apr 3, 2021 at 5:26 AM Euler Taveira <euler@eulerto.com> wrote:
>
> On Thu, Apr 1, 2021, at 7:19 AM, Amit Kapila wrote:
>
> This new patch set version has 2 patches that is because there are 2 separate
> changes: parse_output_parameters() refactor and logical decoding message
> support.
>

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

Let me know what you think? I am planning to push this tomorrow unless
you or someone else has any comments.

-- 
With Regards,
Amit Kapila.

Commits

  1. Allow pgoutput to send logical decoding messages.

  2. Refactor function parse_output_parameters.