Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Dave Cramer <davecramer(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Any objections to implementing LogicalDecodeMessageCB for pgoutput?
Date: 2020-07-24 16:16:33
Message-ID: 20200724161633.ts3olg4hotwsrxew@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-24 16:17:11 Mark unconditionally-safe implicit coercions as leakproof
Previous Message Stephen Frost 2020-07-24 16:05:35 Missing CFI in hlCover()?