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

From Andres Freund
Subject Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Date
Msg-id 20200724161633.ts3olg4hotwsrxew@alap3.anarazel.de
Whole thread Raw
In response to Any objections to implementing LogicalDecodeMessageCB for pgoutput?  (Dave Cramer <davecramer@gmail.com>)
List pgsql-hackers
Hi,

On 2020-07-24 11:33:52 -0400, Dave Cramer wrote:
> For logical replication there is no need to implement this, but others are
> using the pgoutput plugin for Change Data Capture. The reason they are
> using pgoutput is because it is guaranteed to be available as it is in core
> postgres.
> 
> Implementing LogicalDecodeMessageCB provides some synchronization facility
> that is not easily replicated.

It's definitely useful. Probably needs to be parameter that signals
whether they should be sent out?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Missing CFI in hlCover()?
Next
From: Tom Lane
Date:
Subject: Mark unconditionally-safe implicit coercions as leakproof