Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput? - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Date
Msg-id CAA4eK1KT5a6Z+mjphT5ZaMn78eD6RcHRWWcsAkNPiWgUooeqfw@mail.gmail.com
Whole thread Raw
In response to Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?  ("Euler Taveira" <euler@eulerto.com>)
Responses Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
List 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.



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: multi-install PostgresNode fails with older postgres versions
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Stronger safeguard for archive recovery not to miss data