Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Dave Cramer <davecramer@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-07-24T16:16:33Z
Lists: 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



Commits

  1. Allow pgoutput to send logical decoding messages.

  2. Refactor function parse_output_parameters.